[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2024041508-refocus-cycling-09e8@gregkh>
Date: Mon, 15 Apr 2024 09:33:27 +0200
From: Greg KH <greg@...ah.com>
To: Holger Hoffstätte <holger@...lied-asynchrony.com>
Cc: Naohiro Aota <Naohiro.Aota@....com>,
Linux regressions mailing list <regressions@...ts.linux.dev>,
David Sterba <dsterba@...e.com>, Qu Wenruo <wqu@...e.com>,
"linux-btrfs@...r.kernel.org" <linux-btrfs@...r.kernel.org>,
Hiroshi Takekawa <sian@....or.jp>, Chris Mason <clm@...com>,
Josef Bacik <josef@...icpanda.com>,
LKML <linux-kernel@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: btrfs: sanity tests fails on 6.8.3
On Mon, Apr 15, 2024 at 09:25:58AM +0200, Holger Hoffstätte wrote:
> On 2024-04-15 07:24, Naohiro Aota wrote:
> > On Mon, Apr 15, 2024 at 07:11:15AM +0200, Linux regression tracking (Thorsten Leemhuis) wrote:
> > > [adding the authors of the two commits mentioned as well as the Btrfs
> > > maintainers and the regressions & stable list to the list of recipients]
> > >
> > > On 15.04.24 05:56, Hiroshi Takekawa wrote:
> > > >
> > > > Module loading fails with CONFIG_BTRFS_FS_RUN_SANITY_TESTS enabled on
> > > > 6.8.3-6.8.6.
> > > >
> > > > Bisected:
> > > > Reverting these commits, then module loading succeeds.
> > > > 70f49f7b9aa3dfa70e7a2e3163ab4cae7c9a457a
> > >
> > > FWIW, that is a linux-stable commit-id for 41044b41ad2c8c ("btrfs: add
> > > helper to get fs_info from struct inode pointer") [v6.9-rc1, v6.8.3
> > > (70f49f7b9aa3df)]
> > >
> > > > 86211eea8ae1676cc819d2b4fdc8d995394be07d
> >
> > It looks like the stable tree lacks this commit, which is necessary for the
> > commit above.
> >
> > b2136cc288fc ("btrfs: tests: allocate dummy fs_info and root in test_find_delalloc()")
> >
>
> This was previously reported during the last stable cycle, and the missing
> patch is already queued up. You can see the queue here:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-6.8
Thanks for confirming this, the next 6.8 release should resolve this
issue.
greg k-h
Powered by blists - more mailing lists