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 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 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 :) thanks, greg k-h
