From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Nikolay Borisov <nborisov@suse.com>
Cc: "Christoph Hellwig" <hch@lst.de>, "Greg KH" <greg@kroah.com>,
"Holger Hoffstätte" <holger@applied-asynchrony.com>,
stable@vger.kernel.org, linux-xfs@vger.kernel.org,
"Brian Foster" <bfoster@redhat.com>
Subject: Re: request for inclusion of 04197b341f23 ("xfs: don't BUG() on mixed direct and mapped I/O")
Date: Tue, 25 Jul 2017 08:45:48 -0700 [thread overview]
Message-ID: <20170725154548.GO4352@magnolia> (raw)
In-Reply-To: <8639f3da-77f4-6330-40f5-3c3d9cbfbc06@suse.com>
On Tue, Jul 25, 2017 at 05:02:54PM +0300, Nikolay Borisov wrote:
>
>
> On 25.07.2017 16:50, Christoph Hellwig wrote:
> > On Tue, Jul 25, 2017 at 06:47:45AM -0700, Greg KH wrote:
> >> Oh, and I need an ack from the xfs maintainers to be able to take this,
> >> there must be some reason they didn't backport it like they did for a
> >> number of other xfs patches...
> >
> > In general we'd like to see xfstests runs for all stable backports,
> > because file system code is hairy.
> >
> > So for any xfs stable backports please send the list of patches you
> > want backported, and tell us that you did indeed run xfstests. No
> > proof is required, we'd like to trust our contributors.
> >
>
> Before including this in our enterprise distribution I did run xfstest
> with and without the patch and there was no difference in the result.
> Hence I sent the patch.
Looks fine to me...
Acked-by: Darrick J. Wong <darrick.wong@oracle.com>
--D
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-07-25 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 6:47 request for inclusion of 04197b341f23 ("xfs: don't BUG() on mixed direct and mapped I/O") Nikolay Borisov
2017-07-25 10:43 ` Holger Hoffstätte
2017-07-25 10:44 ` Nikolay Borisov
2017-07-25 13:42 ` Greg KH
2017-07-25 13:42 ` Greg KH
2017-07-25 13:43 ` Greg KH
2017-07-25 13:43 ` Greg KH
2017-07-25 13:47 ` Greg KH
2017-07-25 13:47 ` Greg KH
2017-07-25 13:50 ` Christoph Hellwig
2017-07-25 14:02 ` Nikolay Borisov
2017-07-25 15:45 ` Darrick J. Wong [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=20170725154548.GO4352@magnolia \
--to=darrick.wong@oracle.com \
--cc=bfoster@redhat.com \
--cc=greg@kroah.com \
--cc=hch@lst.de \
--cc=holger@applied-asynchrony.com \
--cc=linux-xfs@vger.kernel.org \
--cc=nborisov@suse.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.