From: Dave Chinner <dchinner@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Eduardo Valentin <eduval@amazon.com>,
Stable <stable@vger.kernel.org>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Eric Sandeen <sandeen@sandeen.net>
Subject: Re: [RESEND] requests for xfs patches inclusion in 4.14.y
Date: Wed, 8 Aug 2018 18:57:18 +1000 [thread overview]
Message-ID: <20180808085718.GG20351@rh> (raw)
In-Reply-To: <20180808063529.GB21903@kroah.com>
On Wed, Aug 08, 2018 at 08:35:29AM +0200, Greg KH wrote:
> On Wed, Aug 08, 2018 at 08:46:02AM +1000, Dave Chinner wrote:
> > On Tue, Aug 07, 2018 at 04:19:21PM +0200, Greg KH wrote:
> > > On Wed, Aug 01, 2018 at 05:28:16PM -0700, Eduardo Valentin wrote:
> > > > Greg,
> > > >
> > > > Please consider adding the following XFS patches on linux-4.14.y branch
> > > > to fix NULL pointer dereference errors in lookup_slow() on a NULL inode->i_ops
> > > > and for a corrupted xfs image after xfs_da_shrink_inode():
> > > >
> > > > ee457001ed6c ("xfs: catch inode allocation state mismatch corruption")
> > > > afca6c5b2595 ("xfs: validate cached inodes are free when allocated")
> > > > bb3d48dcf86a ("xfs: don't call xfs_da_shrink_inode with NULL bp")
> > >
> > > Some of these also belong in 4.17...
> > >
> > > Now queued up, thanks.
> >
> > Who's tested the backports?
>
> In the previous thread for this series, Eduardo said that he did.
>
> Eduardo, that is correct, right?
Tested them on 4.14 or 4.17? Testing a backport on one kernel
version doesn't mean it'll be fine in all stable kernels...
Cheers,
Dave.
--
Dave Chinner
dchinner@redhat.com
prev parent reply other threads:[~2018-08-08 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 0:28 [RESEND] requests for xfs patches inclusion in 4.14.y Eduardo Valentin
2018-08-07 14:19 ` Greg KH
2018-08-07 22:46 ` Dave Chinner
2018-08-08 6:35 ` Greg KH
2018-08-08 8:57 ` Dave Chinner [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=20180808085718.GG20351@rh \
--to=dchinner@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=eduval@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=sandeen@sandeen.net \
--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).