From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Andre Noll <maan@tuebingen.mpg.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-xfs@vger.kernel.org, stable@vger.kernel.org
Subject: Re: xfs: Assertion failed in xfs_ag_resv_init()
Date: Thu, 2 May 2019 08:11:07 +1000 [thread overview]
Message-ID: <20190501221107.GI29573@dread.disaster.area> (raw)
In-Reply-To: <20190501192822.GM5207@magnolia>
On Wed, May 01, 2019 at 12:28:22PM -0700, Darrick J. Wong wrote:
> On Wed, May 01, 2019 at 07:51:29PM +0200, Andre Noll wrote:
> > On Wed, May 01, 19:15, Greg Kroah-Hartman wrote
> > > On Wed, May 01, 2019 at 06:59:33PM +0200, Andre Noll wrote:
> > > > On Wed, May 01, 08:36, Darrick J. Wong wrote
> > > > > > > You could send this patch to the stable list, but my guess is that
> > > > > > > they'd prefer a straight backport of all three commits...
> > > > > >
> > > > > > Hm, cherry-picking the first commit onto 4.9,171 already gives
> > > > > > four conflicting files. The conflicts are trivial to resolve (git
> > > > > > cherry-pick -xX theirs 21ec54168b36 does it), but that doesn't
> > > > > > compile because xfs_btree_query_all() is missing. So e9a2599a249ed
> > > > > > (xfs: create a function to query all records in a btree) is needed as
> > > > > > well. But then, applying 86210fbebae (xfs: move various type verifiers
> > > > > > to common file) on top of that gives non-trivial conflicts.
> > > > >
> > > > > Ah, I suspected that might happen. Backports are hard. :(
> > > > >
> > > > > I suppose one saving grace of the patch you sent is that it'll likely
> > > > > break the build if anyone ever /does/ attempt a backport of those first
> > > > > two commits. Perhaps that is the most practical way forward.
> > > > >
> > > > > > So, for automatic backporting we would need to cherry-pick even more,
> > > > > > and each backported commit should be tested of course. Given this, do
> > > > > > you still think Greg prefers a rather large set of straight backports
> > > > > > over the simple commit that just pulls in the missing function?
> > > > >
> > > > > I think you'd have to ask him that, if you decide not to send
> > > > > yesterday's patch.
> > > >
> > > > Let's try. I've added a sentence to the commit message which explains
> > > > why a straight backport is not practical, and how to proceed if anyone
> > > > wants to backport the earlier commits.
> > > >
> > > > Greg: Under the given circumstances, would you be willing to accept
> > > > the patch below for 4.9?
> > >
> > > If the xfs maintainers say this is ok, it is fine with me.
> >
> > Darrick said, he's in favor of the patch, so I guess I can add his
> > Acked-by. Would you also like to see the ack from Dave (the author
> > of the original commit)?
>
> FWIW it seems fine to me, though Dave [cc'd] might have stronger opinions...
Only thing I care about is whether it is QA'd properly. Greg, Sasha,
is the 4.9 stable kernel having fstests run on it as part of the
release gating?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2019-05-01 22:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190430121420.GW2780@tuebingen.mpg.de>
[not found] ` <20190430151151.GF5207@magnolia>
[not found] ` <20190430162506.GZ2780@tuebingen.mpg.de>
[not found] ` <20190430174042.GH5207@magnolia>
[not found] ` <20190430190525.GB2780@tuebingen.mpg.de>
[not found] ` <20190430191825.GF5217@magnolia>
[not found] ` <20190430210724.GD2780@tuebingen.mpg.de>
[not found] ` <20190501153643.GL5207@magnolia>
2019-05-01 16:59 ` xfs: Assertion failed in xfs_ag_resv_init() Andre Noll
2019-05-01 17:15 ` Greg Kroah-Hartman
2019-05-01 17:51 ` Andre Noll
2019-05-01 19:28 ` Darrick J. Wong
2019-05-01 22:11 ` Dave Chinner [this message]
2019-05-02 11:44 ` Greg Kroah-Hartman
2019-05-02 11:45 ` Greg Kroah-Hartman
2019-05-02 13:20 ` Sasha Levin
2019-05-02 14:10 ` Greg Kroah-Hartman
2019-05-02 15:27 ` Andre Noll
2019-05-02 16:52 ` Greg Kroah-Hartman
2019-05-02 17:45 ` Andre Noll
2019-05-02 17:55 ` Sasha Levin
2019-05-02 12:34 ` Sasha Levin
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=20190501221107.GI29573@dread.disaster.area \
--to=david@fromorbit.com \
--cc=darrick.wong@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-xfs@vger.kernel.org \
--cc=maan@tuebingen.mpg.de \
--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).