[Re: [PATCH 0/1] RFC: linux-5.15.y ksmbd backport for CVE-2023-38431] On 12/12/2023 (Tue 21:04) Greg KH wrote: > On Tue, Dec 12, 2023 at 01:47:44PM -0500, paul.gortmaker@xxxxxxxxxxxxx wrote: > > From: Paul Gortmaker <paul.gortmaker@xxxxxxxxxxxxx> > > > > This is a bit long, but I've never touched this code and all I can do is > > compile test it. So the below basically represents a capture of my > > thought process in fixing this for the v5.15.y-stable branch. > > Nice work, but really, given that there are _SO_ many ksmb patches that > have NOT been backported to 5.15.y, I would strongly recommend that we > just mark the thing as depending on BROKEN there for now as your one I'd be 100% fine with that. Can't speak for anyone else though. > backport here is not going to make a dent in the fixes that need to be > applied there to resolve the known issues that the codebase currently > has resolved in newer kernels. > > Do you use this codebase on 5.15.y? What drove you to want to backport I don't use it, and I don't know of anyone who does. > this, just the presence of a random CVE identifier? If that's all it > takes to get companies to actually do backports, maybe I should go > allocate more of them :) I wouldn't have normally touched it but someone else was looking at doing the backport and essentially declared it "too hard" and so I couldn't let that stand. :-P Paul. -- > > thanks, > > greg k-h
