On Tue, Mar 29, 2022 at 11:24 PM Amir Goldstein <amir73il@xxxxxxxxx> wrote: > > On Tue, Mar 8, 2022 at 6:40 PM Theodore Ts'o <tytso@xxxxxxx> wrote: > > > > On Tue, Mar 08, 2022 at 11:08:48AM +0100, Greg KH wrote: > > > > When one looks at xfstest bug reports on the list for xfs on kernels > v4.19 > > > > one has to wonder if using xfs on kernels v5.x.y is a wise choice. > > > > > > That's up to the xfs maintainers to discuss. > > > > > > > Which makes me wonder: how do the distro kernel maintainers keep up > > > > with xfs fixes? > > > > > > Who knows, ask the distro maintainers that use xfs. What do they do? > > > > This is something which is being worked, so I'm not sure we'll need to > > discuss the specifics of the xfs stable backports at LSF/MM. I'm > > hopeful that by May, we'll have come to some kind of resolution of > > that topic. > > > > One of my team members has been working with Darrick to set up a set > > of xfs configs[1] recommended by Darrick, and she's stood up an > > automated test spinner using gce-xfstests which can watch a git branch > > and automatically kick off a set of tests whenever it is updated. > > Sasha has also provided her with a copy of his scripts so we can do > > automated cherry picks of commits with Fixes tags. So the idea is > > that we can, hopefully in a mostly completely automated fashion, > > Here is a little gadget I have been working on in my spare time, > that might be able to assist us in the process of selecting stable > patch candidates. > > Many times, the relevant information for considering a patch for > stable tree is in the cover letter of the patch series. It is also a lot > more efficient to skim over 23 cover letter subjects than it is to skim > over 103 commits of the xfs pull request for 5.15 [2]. > > I've added the command "b4 rn" [1] to produce a list of lore links > to patch series from a PULL request to Linus. > > This gadget could be improved to interactively select the patch > series from within a PR to be saved into an mbox. > > In any case, I do intend to start surveying the xfs patches that got > merged since v5.10 and stage a branch with my own selections, so we > will be able to compare my selections to Shasha's AUTOSEL selections. > FYI, I've enhanced the "br rn" gadget to report fstests that were mentioned on ML discussions on the patch sets, for example: -- - [PATCH 1/3] mm: Add kvrealloc() [https://lore.kernel.org/r/20210714023440.2608690-2-david@xxxxxxxxxxxxx] Tests: generic/040 generic/041 -- This can help to understand if some fstests failure seen on LTS baseline run may already have a fix upstream that could be backported. You can see example release notes for XFS v5.10..v5.17 [1] and the subset of fixes [2] manually selected for my 5.10.y backport branch [3]. I am working with Luis so start testing these backports with his kdevops [4] framework. Thanks, Amir. [1] https://github.com/amir73il/b4/blob/xfs-5.10.y/xfs-5.10..5.17-rn.rst [2] https://github.com/amir73il/b4/blob/xfs-5.10.y/xfs-5.10..5.17-fixes.rst [3] https://github.com/amir73il/linux/commits/xfs-5.10.y [4] https://github.com/mcgrof/kdevops
