From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>, Greg Edwards <gedwards@ddn.com>
Cc: linux-fsdevel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] fs: guard_bio_eod() needs to consider partitions
Date: Fri, 10 Nov 2017 08:25:35 -0700 [thread overview]
Message-ID: <d5c8e16f-6346-c264-ff90-a3c5492e92ad@kernel.dk> (raw)
In-Reply-To: <20171110084629.GA4679@lst.de>
On 11/10/2017 01:46 AM, Christoph Hellwig wrote:
> This looks good to me:
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
>
> Jens, can you pick it up through the block tree given that is where
> the issue was introduced?
I picked it up, and marked it for 4.13 stable as well.
--
Jens Axboe
prev parent reply other threads:[~2017-11-10 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 1:10 [PATCH] fs: guard_bio_eod() needs to consider partitions Greg Edwards
2017-10-24 2:16 ` Al Viro
2017-10-24 7:46 ` Christoph Hellwig
2017-10-24 15:26 ` Greg Edwards
2017-10-24 17:21 ` [PATCH v2] " Greg Edwards
2017-11-01 17:49 ` Greg Edwards
2017-11-10 8:46 ` Christoph Hellwig
2017-11-10 15:25 ` Jens Axboe [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=d5c8e16f-6346-c264-ff90-a3c5492e92ad@kernel.dk \
--to=axboe@kernel.dk \
--cc=gedwards@ddn.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).