Hi! Furthermore, CIP members should really not be using code from staging. This one looks rather easy to backport. It failed only because reformatting of the printk. Would it make sense to ask why it

Hi! I'm sorry. Warning was clear, but I did not open the email... I was reviewing patches for 5.10.77. Best regards, Pavel

Hi! This seems to be fixed in stable/4.4, too, as 61a811e8f5229264b822361f8b23d7638fd8c914. And cip-kernel-sec says so, good. AFAICT the vulnerability was introduced by 1ef6f7c9390f in 5.9-rc3. But th

Hi! Sorry, I missed the meeting. There are public holidays today, and I'm quite busy this week. From last irc meeting, I was reviewing 5.10.76. Best regards, Pavel

Hi! Others are fixed, but this one may be worth watching. Fortunately it is not remote attack, AFAICT. Best regards, Pavel

Hi! ... I guess we can wait for this to be merged through normal channels. It may make sense to help with this backport. Not sure why this has CVE number. We probably need not care. I guess we don't c

Hi! Thank you, but that board seems to still have problems: https://lava.ciplatform.org/scheduler/job/458108 expect-shell-connection: Wait for prompt ['root@ebsy-isar:~#'] (timeout 00:10:00) Waiting u

Hi! New realtime trees should be available at kernel.org. Trees are available at https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.4.y-cip-rt https://git.kernel.org/pub/

Hi! 4.4.285-rt226 is out it would be good to make it into -cip-rt release. Would it be possible to create 4.4.285-cip release to make it easier? Thanks and best regards, Pavel ----- Forwarded message

Hi! On cip-members, there was question of widely used drivers that we should include for WIFI or Bluetooth. AFAICT there are no standartized interfaces for WIFI, and each vendor has their own. For Blu

Hi! On cip-members there's discussion about quality of selected wireless drivers. AFAICT we are reviewing changes to those drivers on -stable series (good). We are not testing the drivers in any meani

Hi! I guess I should mention alternate possibilities. We could try to somehow "hash" the commits... Perhaps I'd review all the patches where upstream sha begins with 0-6. But patches in -stable often

Hi! It is good to review "stable" patches soon, because such reviews are more useful for the stable community, and because when bug is spotted, it is easier to get patch dropped in the 5.10.X-rc phase

Hi! It is not first time I see this failure: https://lava.ciplatform.org/scheduler/job/444336 [[0;32m OK [0m] Started Login Service. [[0m[0;31m* [0m] (1 of 2) A start job is running for…ate sshd host

Hi! I'm travelling tommorow and day after that, so I may not make it to the irc meeting. I have reviewed patches for 5.10.64, 65 and 66. Best regards, Pavel -- DENX Software Engineering GmbH, Managing

Hi! New realtime trees should be available at kernel.org. Trees are available at https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/log/?h=linux-4.19.y-cip-rt https://git.kernel.org/pub

Hi! I don't think we need to care about this one. Embedded systems don't usually run untrusted code... This is already queued to 4.4 and 4.19; we can simply wait. KVM. Tricky code and not exactly focu

Hi! These summaries are not so short; I simply skip them and go to full list. Perhaps they don't need to be included, or could include only CVEs where we need to take an action? This one is queued for

Hi! Hmm, no; that is what original code did and what is known not to work for reasons I don't fully understand. Anyway, I asked on the lists, and according to Thadeu Lima de Souza Cascardo Ubuntu did

Hi! At least some of the relevant fixes are queued for 5.10.61/4.19. Likely this will resolve itself. I took a look into this. Apparently 4.14 and 4.19 is affected. ( https://seclists.org/oss-sec/2021