On Tue, Mar 08, 2022 at 01:04:05PM +0200, Amir Goldstein wrote: > On Tue, Mar 8, 2022 at 12:08 PM Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > so go take this up with the fs developers :) > > It is easy to blame the "fs developers", but is it also very hard on an > overloaded maintainer to ALSO take care of GOOD stable tree updates. > > Here is a model that seems to be working well for some subsystems: > When a tester/developer finds a bug they write an LTP test. > That LTP test gets run by stable kernel test bots and prompts action > from distros who now know of this issue and may invest resources > in backporting patches. > > If I am seeing random developers reporting bugs from running xfstests > on stable kernels and I am not seeing the stable kernel test bots reporting > those bugs, then there may be room for improvement in the stable kernel > testing process?? I have been investing huge amounts of time to improve this process, to the point you can get fstests going and test against a known baseline on kdevops [0] today with just the following 6 commands (and works with different cloud providers, or local virtualized solutions): make menuconfig make make bringup make linux make fstest make fstest-baseline The baseline is what still takes time to create, and so with that it should in theory be possible to get the average Joe to at least help start testing a filesystem easily. Patches welcomed. In so far as actually getting more patches into stable for XFS, it is just about doing the actual work of thorough review and then ensuring it doesn't break the baseline. It does require time and effort, but hopefully the above will help. Do you have a series of stable candidates you'd like to review? [0] https://github.com/mcgrof/kdevops Luis
