diff options
| author | Vivek Goyal <vgoyal@redhat.com> | 2015-11-09 09:23:40 -0700 |
|---|---|---|
| committer | Jens Axboe <axboe@fb.com> | 2015-11-11 09:36:57 -0700 |
| commit | dbd3ca50753e70e09cad747dce23b1a7683a3342 (patch) | |
| tree | 7e41970d124767b0184baae1d339ac2d6995f080 /block/blk-core.c | |
| parent | c74dc7801d515d01847fd5cf2b472489fa5717b1 (diff) | |
| download | lwn-dbd3ca50753e70e09cad747dce23b1a7683a3342.tar.gz lwn-dbd3ca50753e70e09cad747dce23b1a7683a3342.zip | |
fs/block_dev.c: Remove WARN_ON() when inode writeback fails
If a block device is hot removed and later last reference to device
is put, we try to writeback the dirty inode. But device is gone and
that writeback fails.
Currently we do a WARN_ON() which does not seem to be the right thing.
Convert it to a ratelimited kernel warning.
Reported-by: Andi Kleen <andi@firstfloor.org>
Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Acked-by: Tejun Heo <tj@kernel.org>
[jmoyer@redhat.com: get rid of unnecessary name initialization, 80 cols]
Signed-off-by: Jeff Moyer <jmoyer@redhat.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'block/blk-core.c')
0 files changed, 0 insertions, 0 deletions