From: Maurizio Lombardi <mlombard@redhat.com>
To: Jens Axboe <axboe@kernel.dk>, Mike Qiu <qiudayu@linux.vnet.ibm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ming.lei@canonical.com" <ming.lei@canonical.com>,
"dongsu.park@profitbricks.com" <dongsu.park@profitbricks.com>,
"jet.chen@intel.com" <jet.chen@intel.com>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"hch@lst.de" <hch@lst.de>,
"kmo@daterainc.com" <kmo@daterainc.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"axboe@fb.com" <axboe@fb.com>
Subject: Re: Bug_ON with patch: bio: modify __bio_add_page() to accept pages that don't start a new segment
Date: Wed, 16 Jul 2014 08:51:09 +0200 [thread overview]
Message-ID: <53C620DD.7090700@redhat.com> (raw)
In-Reply-To: <53C4E9F1.7070302@redhat.com>
Hi,
On 07/15/2014 10:44 AM, Maurizio Lombardi wrote:
>> I have reverted it yesterday in my tree.
>>
>
>
> The problem was here:
>
> if (q->merge_bvec_fn) {
> struct bvec_merge_data bvm = {
> .bi_bdev = bio->bi_bdev,
> .bi_sector = bio->bi_iter.bi_sector,
> .bi_size = bio->bi_iter.bi_size, <-------
> .bi_rw = bio->bi_rw,
> };
>
> /*
> * merge_bvec_fn() returns number of bytes it can accept
> * at this offset
> */
> if (q->merge_bvec_fn(q, &bvm, bvec) < bvec->bv_len)
> goto failed;
> }
>
> /* If we may be able to merge these biovecs, force a recount */
> if (bio->bi_vcnt > 1 && (BIOVEC_PHYS_MERGEABLE(bvec-1, bvec)))
> bio->bi_flags &= ~(1 << BIO_SEG_VALID);
>
>
> it should have been ".bi_size = bio->bi_iter.bi_size - len"
>
Jens, will you restore the patch in your tree if I submit
this fix?
Thanks,
Maurizio Lombardi
next prev parent reply other threads:[~2014-07-16 6:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 8:14 Bug_ON with patch: bio: modify __bio_add_page() to accept pages that don't start a new segment Mike Qiu
2014-07-15 8:41 ` Jens Axboe
2014-07-15 8:42 ` Mike Qiu
2014-07-15 8:44 ` Maurizio Lombardi
2014-07-16 6:51 ` Maurizio Lombardi [this message]
2014-07-16 7:53 ` Jens Axboe
2014-07-22 14:08 ` Maurizio Lombardi
2014-07-15 11:38 ` Maurizio Lombardi
2014-07-15 12:01 ` Maurizio Lombardi
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=53C620DD.7090700@redhat.com \
--to=mlombard@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@fb.com \
--cc=axboe@kernel.dk \
--cc=dongsu.park@profitbricks.com \
--cc=hch@lst.de \
--cc=jet.chen@intel.com \
--cc=kmo@daterainc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=qiudayu@linux.vnet.ibm.com \
--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