block: don't force stable writes for non-integrity metadata

There is no need to force stable writes if we are only using
non-integrity metadata

Signed-off-by: Christoph Hellwig <hch@lst.de>

diff --git a/block/blk-integrity.c b/block/blk-integrity.c
index 3291f861072d2352097fe7b23967fdb739bc5b00..2a34eeae9c08d8527972d8fb0e1048bc2bb83f25 100644 (file)
--- a/block/blk-integrity.c
+++ b/block/blk-integrity.c
@@ -399,7 +399,8 @@ void blk_integrity_register(struct gendisk *disk, struct blk_integrity *template
        bi->tuple_size = template->tuple_size;
        bi->tag_size = template->tag_size;
 
-       blk_queue_flag_set(QUEUE_FLAG_STABLE_WRITES, disk->queue);
+       if (bi->profile->verify_fn || bi->profile->generate_fn)
+               blk_queue_flag_set(QUEUE_FLAG_STABLE_WRITES, disk->queue);
 
 #ifdef CONFIG_BLK_INLINE_ENCRYPTION
        if (disk->queue->crypto_profile) {