From: David Sterba <dsterba@suse.cz>
To: Jens Axboe <axboe@kernel.dk>
Cc: Ming Lei <tom.leiming@gmail.com>, Liu Bo <bo.li.liu@oracle.com>,
Filipe Manana <FdManana@suse.com>,
linux-block <linux-block@vger.kernel.org>
Subject: Re: [PATCH] block: note about cloned bios and bio_for_each_segment_all
Date: Sat, 15 Jul 2017 02:28:22 +0200 [thread overview]
Message-ID: <20170715002822.GL2866@suse.cz> (raw)
In-Reply-To: <06376146-e4c3-efd6-8893-155052b14034@kernel.dk>
On Fri, Jul 14, 2017 at 08:22:31AM -0600, Jens Axboe wrote:
> /*
> * drivers should _never_ use the all version - the bio may have been split
> - * before it got to the driver and the driver won't own all of it
> + * before it got to the driver and the driver won't own all of it.
> + *
> + * Don't use this on cloned bio's.
> */
> #define bio_for_each_segment_all(bvl, bio, i) \
> + WARN_ON_ONCE(bio_flagged(bio, BIO_CLONED)); \
> for (i = 0, bvl = (bio)->bi_io_vec; i < (bio)->bi_vcnt; i++, bvl++)
This needs a multiline statement protection, otherwise
if (...)
bio_for_each_segment_all(...) {
...
}
would expand to
if (...)
WARN_ON_ONCE(...);
bio_for_each_segment_all(...) { ... }
However "do { ... } while(0)" cannot be used here, so WARN_ON_ONCE could
be moved to the initialization block of for:
#define bio_for_each_segment_all(bvl, bio, i) \
for (WARN_ON_ONCE(bio_flagged(bio, BIO_CLONED)), \
i = 0, bvl = (bio)->bi_io_vec; i < (bio)->bi_vcnt; i++, bvl++)
I haven't found any code using the exact broken pattern. So this does
not explain the crash Liu Bo reports.
next prev parent reply other threads:[~2017-07-15 0:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 13:40 [PATCH] block: note about cloned bios and bio_for_each_segment_all David Sterba
2017-07-14 13:47 ` Ming Lei
2017-07-14 14:22 ` Jens Axboe
2017-07-14 20:54 ` Liu Bo
2017-07-14 22:35 ` Ming Lei
2017-07-14 22:37 ` Jens Axboe
2017-07-14 23:20 ` Liu Bo
2017-07-18 22:19 ` Bart Van Assche
2017-07-24 16:19 ` Peter Zijlstra
2017-07-15 0:28 ` David Sterba [this message]
2017-07-14 15:03 ` David Sterba
2017-07-14 17:56 ` Filipe Manana
2017-07-14 18:19 ` 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=20170715002822.GL2866@suse.cz \
--to=dsterba@suse.cz \
--cc=FdManana@suse.com \
--cc=axboe@kernel.dk \
--cc=bo.li.liu@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=tom.leiming@gmail.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