From: Hannes Reinecke <hare@suse.de>
To: Ming Lei <ming.lei@canonical.com>, Jens Axboe <axboe@fb.com>,
linux-kernel@vger.kernel.org
Cc: linux-block@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Kent Overstreet <kent.overstreet@gmail.com>,
"4.3+" <stable@vger.kernel.org>, Shaohua Li <shli@fb.com>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH v2] block: make sure big bio is splitted into at most 256 bvecs
Date: Fri, 10 Jun 2016 13:37:17 +0200 [thread overview]
Message-ID: <575AA66D.5010407@suse.de> (raw)
In-Reply-To: <1465556858-30949-1-git-send-email-ming.lei@canonical.com>
On 06/10/2016 01:07 PM, Ming Lei wrote:
> After arbitrary bio size is supported, the incoming bio may
> be very big. We have to split the bio into small bios so that
> each holds at most BIO_MAX_PAGES bvecs for safety reason, such
> as bio_clone().
>
> This patch fixes the following kernel crash:
>
>> [ 172.660142] BUG: unable to handle kernel NULL pointer dereference at 0000000000000028
>> [ 172.660229] IP: [<ffffffff811e53b4>] bio_trim+0xf/0x2a
>> [ 172.660289] PGD 7faf3e067 PUD 7f9279067 PMD 0
>> [ 172.660399] Oops: 0000 [#1] SMP
>> [...]
>> [ 172.664780] Call Trace:
>> [ 172.664813] [<ffffffffa007f3be>] ? raid1_make_request+0x2e8/0xad7 [raid1]
>> [ 172.664846] [<ffffffff811f07da>] ? blk_queue_split+0x377/0x3d4
>> [ 172.664880] [<ffffffffa005fb5f>] ? md_make_request+0xf6/0x1e9 [md_mod]
>> [ 172.664912] [<ffffffff811eb860>] ? generic_make_request+0xb5/0x155
>> [ 172.664947] [<ffffffffa0445c89>] ? prio_io+0x85/0x95 [bcache]
>> [ 172.664981] [<ffffffffa0448252>] ? register_cache_set+0x355/0x8d0 [bcache]
>> [ 172.665016] [<ffffffffa04497d3>] ? register_bcache+0x1006/0x1174 [bcache]
>
> The issue can be reproduced by the following steps:
> - create one raid1 over two virtio-blk
> - build bcache device over the above raid1 and another cache device
> and bucket size is set as 2Mbytes
> - set cache mode as writeback
> - run random write over ext4 on the bcache device
>
> Fixes: 54efd50(block: make generic_make_request handle arbitrarily sized bios)
> Reported-by: Sebastian Roesner <sroesner-kernelorg@roesner-online.de>
> Reported-by: Eric Wheeler <bcache@lists.ewheeler.net>
> Cc: stable@vger.kernel.org (4.3+)
> Cc: Shaohua Li <shli@fb.com>
> Acked-by: Kent Overstreet <kent.overstreet@gmail.com>
> Signed-off-by: Ming Lei <ming.lei@canonical.com>
> ---
> V2:
> - don't mark as REQ_NOMERGE in case the bio is splitted
> for reaching the limit of bvecs count
> V1:
> - Kent pointed out that using max io size can't cover
> the case of non-full bvecs/pages
> block/blk-merge.c | 35 ++++++++++++++++++++++++++++++++---
> 1 file changed, 32 insertions(+), 3 deletions(-)
>
Hmm. So everybody is suffering because someone _might_ be using bio_clone?
Why can't we fixup bio_clone() (or the callers of which) to correctly
set the queue limits?
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2016-06-10 11:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 11:07 [PATCH v2] block: make sure big bio is splitted into at most 256 bvecs Ming Lei
2016-06-10 11:37 ` Hannes Reinecke [this message]
2016-06-10 14:16 ` Ming Lei
2016-06-13 15:46 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2016-04-06 3:43 [PATCH v1] " Ming Lei
2016-08-11 6:33 ` [PATCH v2] " Eric Wheeler
2016-08-11 14:02 ` Christoph Hellwig
2016-08-12 11:12 ` Ming Lei
2016-08-12 16:36 ` Kent Overstreet
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=575AA66D.5010407@suse.de \
--to=hare@suse.de \
--cc=axboe@fb.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=kent.overstreet@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=shli@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox