summaryrefslogtreecommitdiffstats
path: root/arch/sh/kernel
diff options
context:
space:
mode:
authorLu Fengqi <lufq.fnst@cn.fujitsu.com>2017-08-18 16:38:07 +0800
committerDavid Sterba <dsterba@suse.com>2017-08-21 17:47:42 +0200
commit43a0111103af2d358f6d2d671d8429ba169e53bb (patch)
tree7c522684df69717088ac04fe3927aead2ac1ad31 /arch/sh/kernel
parent72610b1b40005fa19a107ea62b8bcc0ca84ef11b (diff)
downloadop-kernel-dev-43a0111103af2d358f6d2d671d8429ba169e53bb.zip
op-kernel-dev-43a0111103af2d358f6d2d671d8429ba169e53bb.tar.gz
btrfs: use btrfsic_submit_bio instead of submit_bio in write_dev_flush
Although this bio has no data attached, it will reach this condition (bio->bi_opf & REQ_PREFLUSH) and then update the flush_gen of dev_state in __btrfsic_submit_bio. So we should still submit it through integrity checker. Otherwise, the integrity checker will throw the following warning when I mount a newly created btrfs filesystem. [10264.755497] btrfs: attempt to write superblock which references block M @29523968 (sdb1/1111654400/0) which is not flushed out of disk's write cache (block flush_gen=1, dev->flush_gen=0)! [10264.755498] btrfs: attempt to write superblock which references block M @29523968 (sdb1/37912576/0) which is not flushed out of disk's write cache (block flush_gen=1, dev->flush_gen=0)! Signed-off-by: Lu Fengqi <lufq.fnst@cn.fujitsu.com> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'arch/sh/kernel')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud