From: Greg KH <gregkh@linuxfoundation.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Christoph Hellwig <hch@lst.de>, stable <stable@vger.kernel.org>,
Dave Chinner <david@fromorbit.com>,
Anders Blomdell <anders.blomdell@gmail.com>,
linux-xfs@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Chandan Babu R <chandan.babu@oracle.com>
Subject: Re: XFS mount timeout in linux-6.9.11
Date: Sun, 8 Sep 2024 16:18:18 +0200 [thread overview]
Message-ID: <2024090803-twerp-moaning-2bf6@gregkh> (raw)
In-Reply-To: <2ca27751aba7c9f74c13facc7ffbbb1934dac59c.camel@infradead.org>
On Wed, Sep 04, 2024 at 08:45:14AM +0100, David Woodhouse wrote:
> On Tue, 2024-08-13 at 08:25 -0700, Darrick J. Wong wrote:
> > On Tue, Aug 13, 2024 at 04:59:25PM +0200, Christoph Hellwig wrote:
> > > On Tue, Aug 13, 2024 at 07:19:28PM +1000, Dave Chinner wrote:
> > > > In hindsight, this was a wholly avoidable bug - a single patch made
> > > > two different API modifications that only differed by a single
> > > > letter, and one of the 23 conversions missed a single letter. If
> > > > that was two patches - one for the finobt conversion, the second for
> > > > the inobt conversion, the bug would have been plainly obvious during
> > > > review....
> > >
> > > Maybe we should avoid identifiers that close anyway :)
> > >
> > > The change looks good:
> > >
> > > Reviewed-by: Christoph Hellwig <hch@lst.de>
> >
> > Looks good to me too
> > Reviewed-by: Darrick J. Wong <djwong@kernel.org>
>
> Is it (now commit 95179935bea) going to -stable too?
It's in the 6.10.y queue now, thanks!
greg k-h
prev parent reply other threads:[~2024-09-08 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <71864473-f0f7-41c3-95f2-c78f6edcfab9@gmail.com>
[not found] ` <ZraeRdPmGXpbRM7V@dread.disaster.area>
[not found] ` <252d91e2-282e-4af4-b99b-3b8147d98bc3@gmail.com>
[not found] ` <ZrfzsIcTX1Qi+IUi@dread.disaster.area>
[not found] ` <4697de37-a630-402f-a547-cc4b70de9dc3@gmail.com>
[not found] ` <ZrlRggozUT6dJRh+@dread.disaster.area>
[not found] ` <6a19bfdf-9503-4c3b-bc5b-192685ec1bdd@gmail.com>
[not found] ` <ZrslIPV6/qk6cLVy@dread.disaster.area>
[not found] ` <20240813145925.GD16082@lst.de>
[not found] ` <20240813152530.GF6051@frogsfrogsfrogs>
2024-09-04 7:45 ` XFS mount timeout in linux-6.9.11 David Woodhouse
2024-09-08 14:18 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2024090803-twerp-moaning-2bf6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=anders.blomdell@gmail.com \
--cc=chandan.babu@oracle.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=dwmw2@infradead.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).