From: Mike Snitzer <snitzer@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: NeilBrown <neilb@suse.com>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
Ming Lei <ming.lei@redhat.com>
Subject: Re: why does __split_and_process_bio use bio_clone_bioset?
Date: Fri, 15 Jun 2018 14:26:31 -0400 [thread overview]
Message-ID: <20180615182631.GA6906@redhat.com> (raw)
In-Reply-To: <20180615073846.GA29726@infradead.org>
On Fri, Jun 15 2018 at 3:38am -0400,
Christoph Hellwig <hch@infradead.org> wrote:
> On Thu, Jun 14, 2018 at 04:08:09PM -0400, Mike Snitzer wrote:
> > The patch below seems to work fine (given quick testing).. It also has a
> > side-effect of not breaking integrity support (which commit 18a25da8
> > appears to do because it isn't accounting for any of the integrity stuff
> > bio_split, or dm.c:clone_bio, does).
>
> Looks sensible to me. Are you going to queue this up for 4.18?
Yes. Already queued, likely won't send to Linus until end of next week
though.. unless you want it upstream sooner?
https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=dm-4.18&id=bbb683cf88f58742233c3551d1b9839a5fe5bbf8
next prev parent reply other threads:[~2018-06-15 18:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 8:19 why does __split_and_process_bio use bio_clone_bioset? Christoph Hellwig
2018-06-14 18:12 ` Mike Snitzer
2018-06-14 20:08 ` Mike Snitzer
2018-06-14 23:34 ` [dm-devel] " NeilBrown
2018-06-15 7:38 ` Christoph Hellwig
2018-06-15 18:26 ` Mike Snitzer [this message]
2018-06-16 15:20 ` Christoph Hellwig
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=20180615182631.GA6906@redhat.com \
--to=snitzer@redhat.com \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=neilb@suse.com \
/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).