On Tue, 2022-12-27 at 08:37 +0100, Greg KH wrote: > On Tue, Dec 27, 2022 at 09:47:29AM +0800, GUO Zihua wrote: > > [ Upstream commit c7423dbdbc9ecef7fff5239d144cad4b9887f4de ] > > For obvious reasons we can not only take this patch (from 6.2-rc1) into > 4.19.y as that would cause people who upgrade from 4.19.y to a newer > stable kernel to have a regression. > > Please submit backports for all stable kernels if you wish to see this > in older ones to prevent problems like this from happening. Sasha has already queued the original commit and the dependencies for the 6.1, 6.0, and 5.15 stable kernels. Those kernels all had the call_lsm_notifier() to call_blocking_lsm_notifier() change. Prior to 5.3, the change to the blocking notifier would need to be backported as well. This version of the backport still needs to be reviewed. thanks, Mimi > > But also, why are you still on 4.19.y? What is wrong with 5.4.y at this > point in time? If we dropped support for 4.19.y in January, what would > that cause to happen for your systems? > > thanks, > > greg k-h >
