linux-kernel - Re: Linux 5.11-rc4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 18 Jan 2021 19:48:24 -0800
From:   Guenter Roeck <linux@...ck-us.net>
To:     Paul Zimmerman <pauldzim@...il.com>
Cc:     linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org
Subject: Re: Linux 5.11-rc4

On 1/18/21 7:35 PM, Paul Zimmerman wrote:
> On Mon, Jan 18, 2021 at 14:35:20 -0800, Guenter Roeck wrote:
>> On Sun, Jan 17, 2021 at 04:56:46PM -0800, Linus Torvalds wrote:
>>> Things continue to look fairly normal for this release: 5.11-rc4 is
>>> solidly average in size, and nothing particularly scary stands out.
>>>
>>> In the diff itself, the new ampere modesetting support shows up fairly
>>> clearly - it's one of those hardware enablement things that should be
>>> entirely invisible to people who don't have that hardware, but it does
>>> end up being about a fifth of the whole rc4 patch.
>>>
>>> If you ignore that oddity, the rest looks pretty normal, with random
>>> patches all over, and a lot of it being quite small. All the usual
>>> suspects: drivers (gpu, sound, rdma, md, networking..) arch updates
>>> (arm64, risc-v, x86), fiesystems (ext4, nfs, btrfs), core networking,
>>> documentation and tooling. And just random fixes.
>>>
>>
>> Here are the test results:
>>
>> Build results:
>> 	total: 153 pass: 151 fail: 2
>> Failed builds:
>> 	arm64:allmodconfig
>> 	ia64:defconfig
>> Qemu test results:
>> 	total: 430 pass: 428 fail: 2
>> Failed tests:
>> 	arm:raspi2:multi_v7_defconfig:bcm2836-rpi-2-b:initrd
>> 	arm:raspi2:multi_v7_defconfig:sd:bcm2836-rpi-2-b:rootfs
>>
>> Same old ...
> 
> Hi Guenter,
> 
> Can you give a link to the problem that Qemu is having with RPI2?
> Maybe I can take a look at it.
> 

The fix is pending in -next (and has been there for a while).
Look for "irqchip/bcm2836: Fix IPI acknowledgement after
conversion to handle_percpu_devid_irq" (commit d7f39c40ebb6
in next-20210118).

Guenter