diff options
author | Martin K. Petersen <martin.petersen@oracle.com> | 2010-10-15 15:49:20 +0200 |
---|---|---|
committer | Jens Axboe <jaxboe@fusionio.com> | 2010-10-15 15:49:20 +0200 |
commit | 495d2b3883682fcd1c3dee3a45e38fd00154ae25 (patch) | |
tree | 1d2f76a70fc1c5edbb39769e675b9e468a346d5e /block/blk-core.c | |
parent | e817bf3f68f55e7307c3e9abe5f32d0c05c83988 (diff) | |
download | kernel_samsung_crespo-495d2b3883682fcd1c3dee3a45e38fd00154ae25.zip kernel_samsung_crespo-495d2b3883682fcd1c3dee3a45e38fd00154ae25.tar.gz kernel_samsung_crespo-495d2b3883682fcd1c3dee3a45e38fd00154ae25.tar.bz2 |
block: Make the integrity mapped property a bio flag
Previously we tracked whether the integrity metadata had been remapped
using a request flag. This was fine for low-level retries. However, if
an I/O was redriven by upper layers we would end up remapping again,
causing the retry to fail.
Deprecate the REQ_INTEGRITY flag and introduce BIO_MAPPED_INTEGRITY
which enables filesystems to notify lower layers that the bio in
question has already been remapped.
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Signed-off-by: Jens Axboe <jaxboe@fusionio.com>
Diffstat (limited to 'block/blk-core.c')
0 files changed, 0 insertions, 0 deletions