From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>, linux-block@vger.kernel.org
Subject: Re: [PATCH] block: take destination bvec offsets into account in bio_copy_data_iter
Date: Sat, 28 May 2022 06:52:33 +0200 [thread overview]
Message-ID: <20220528045233.GA13168@lst.de> (raw)
In-Reply-To: <a1e6fd92-ed3d-f94c-43a7-ff4fca27b759@kernel.dk>
On Fri, May 27, 2022 at 08:36:47PM -0600, Jens Axboe wrote:
> On 5/24/22 8:39 AM, Christoph Hellwig wrote:
> > Appartly bcache can copy into bios that do not just contain fresh
> > pages but can have offsets into the bio_vecs. Restore support for tht
> > in bio_copy_data_iter.
> >
> > Fixes: 8b679a070c53 ("block: rewrite bio_copy_data_iter to use bvec_kmap_local and memcpy_to_bvec")
>
> Applied, but where is this sha from? The upstream one is f8b679a070c5.
Apparently from my copy and pasting discarding the initial f of that..
next prev parent reply other threads:[~2022-05-28 4:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 14:39 [PATCH] block: take destination bvec offsets into account in bio_copy_data_iter Christoph Hellwig
2022-05-28 2:36 ` Jens Axboe
2022-05-28 4:52 ` Christoph Hellwig [this message]
2022-05-28 12:24 ` Jens Axboe
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=20220528045233.GA13168@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=linux-block@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).