linux-kernel - Re: [PATCH 5.4 000/167] 5.4.25-stable review

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <2fc1ae97-cb04-7105-b458-cb456732f48e@roeck-us.net>
Date:   Tue, 10 Mar 2020 08:55:54 -0700
From:   Guenter Roeck <linux@...ck-us.net>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org
Cc:     torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
        shuah@...nel.org, patches@...nelci.org,
        ben.hutchings@...ethink.co.uk, lkft-triage@...ts.linaro.org,
        stable@...r.kernel.org
Subject: Re: [PATCH 5.4 000/167] 5.4.25-stable review

On 3/10/20 7:42 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.4.25 release.
> There are 167 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
> 
> Responses should be made by Thu, 12 Mar 2020 14:40:27 +0000.
> Anything received after that time might be too late.
> 

mips:allmodconfig, nds32:allmodconfig, and probably others:

  CC [M]  drivers/gpu/drm/virtio/virtgpu_object.o
drivers/gpu/drm/virtio/virtgpu_object.c:31:67: error: expected ')' before 'int'
   31 | module_param_named(virglhack, virtio_gpu_virglrenderer_workaround, int, 0400);

Culprit is "drm/virtio: make resource id workaround runtime switchable.".
Upstream commit b0138364da17617d ("drm/virtio: module_param_named() requires linux/moduleparam.h")
is tagged 'Fixes: 3e93bc2a58aa ("drm/virtio: make resource id workaround runtime switchable.")'
and does indeed fix this problem.

When patches are auto-selected for backports, would it be possible to also pick
patches fixing them right away ?

Guenter