>>>>> "nab" == Nicholas A Bellinger <[email protected]> writes:
nab> The issue is that existing fs/bio-integrity.c code always assumes nab> client/initiator mode, in that it will attempt to nab> bio_integrity_generate() protection information in the submit_bio nab> WRITE path, and bio_integrity_verify() of protection information in nab> the bio_endio READ completion path. Only if the submit_bio() caller hasn't attached protection information already. If you submit a bio with a bip already attached the block layer will not generate/verify. -- Martin K. Petersen Oracle Linux Engineering -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
