diff options
| author | Ed Cashin <ecashin@coraid.com> | 2009-09-10 22:30:47 +0200 |
|---|---|---|
| committer | Jens Axboe <jens.axboe@oracle.com> | 2009-09-14 08:24:52 +0200 |
| commit | 18d8217bc441630c3c5ec7416c5a65c69e8a0979 (patch) | |
| tree | 9051bbd875dd96d8d75ccf2dfc228e912edfeb50 /block | |
| parent | 01edede41e352e4879a89cdc5468f72ffc89b713 (diff) | |
| download | kernel_samsung_tuna-18d8217bc441630c3c5ec7416c5a65c69e8a0979.zip kernel_samsung_tuna-18d8217bc441630c3c5ec7416c5a65c69e8a0979.tar.gz kernel_samsung_tuna-18d8217bc441630c3c5ec7416c5a65c69e8a0979.tar.bz2 | |
aoe: end barrier bios with EOPNOTSUPP
BugLink: http://bugzilla.kernel.org/show_bug.cgi?id=13942
Bruno Premont noticed that aoe throws a BUG during umount of an XFS in
2.6.31:
[ 5259.349897] aoe: bi_io_vec is NULL
[ 5259.349940] ------------[ cut here ]------------
[ 5259.349958] kernel BUG at /usr/src/linux-2.6/drivers/block/aoe/aoeblk.c:177!
[ 5259.349990] invalid opcode: 0000 [#1]
The bio in question is a barrier. Jens Axboe suggested that such bios
need to be recognized and ended with -EOPNOTSUPP by any driver that
provides its own ->make_request_fn handler and does not handle
barriers.
In testing the changes below eliminate the BUG.
(Better would be real barrier support, something that Ed says he'll add
for later in the .32 cycle. For now, this at least gets rid of a bug
with crashing on an empty barrier. Jens)
Signed-off-by: Ed L. Cashin <ecashin@coraid.com>
Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions