diff options
| author | Jeff Moyer <[email protected]> | 2011-10-17 12:57:22 +0200 |
|---|---|---|
| committer | Jens Axboe <[email protected]> | 2011-10-24 16:24:30 +0200 |
| commit | 834f9f61a525d2f6d3d0c93894e26326c8d3ceed (patch) | |
| tree | 73e973ad0c01ce4ac0317f089c9cbb3707186834 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 456be1484ffc72a24bdb4200b5847c4fa90139d9 (diff) | |
blk-flush: fix invalid BUG_ON in blk_insert_flush
A user reported a regression due to commit
4853abaae7e4a2af938115ce9071ef8684fb7af4 (block: fix flush
machinery for stacking drivers with differring flush flags).
Part of the problem is that blk_insert_flush required a
single bio be attached to the request. In reality, having
no attached bio is also a valid case, as can be observed with
an empty flush.
[1] http://www.redhat.com/archives/dm-devel/2011-September/msg00154.html
Reported-by: Christophe Saout <[email protected]>
Signed-off-by: Jeff Moyer <[email protected]
Acked-by: Tejun Heo <[email protected]>
Stable note: 3.1
Cc: [email protected]
Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions