blk-integrity: support arbitrary buffer alignment#588
Open
blktests-ci[bot] wants to merge 1 commit intolinus-master_basefrom
Open
blk-integrity: support arbitrary buffer alignment#588blktests-ci[bot] wants to merge 1 commit intolinus-master_basefrom
blktests-ci[bot] wants to merge 1 commit intolinus-master_basefrom
Conversation
Author
|
Upstream branch: 6de23f8 |
blktests-ci
bot
force-pushed
the
linus-master_base
branch
from
c90f83b to
c475e20
Compare
Author
|
Upstream branch: 7dff99b |
blktests-ci
bot
force-pushed
the
series/1056653=>linus-master
branch
from
b412689 to
9c4134d
Compare
blktests-ci
bot
force-pushed
the
linus-master_base
branch
from
c475e20 to
14f6b99
Compare
Author
|
Upstream branch: a75cb86 |
blktests-ci
bot
force-pushed
the
series/1056653=>linus-master
branch
from
9c4134d to
19e64d2
Compare
blktests-ci
bot
force-pushed
the
linus-master_base
branch
from
14f6b99 to
856dc37
Compare
Author
|
Upstream branch: 4d349ee |
blktests-ci
bot
force-pushed
the
series/1056653=>linus-master
branch
from
19e64d2 to
551fcd3
Compare
blktests-ci
bot
force-pushed
the
linus-master_base
branch
from
856dc37 to
40967f0
Compare
Author
|
Upstream branch: 11439c4 |
blktests-ci
bot
force-pushed
the
series/1056653=>linus-master
branch
from
551fcd3 to
b689ffa
Compare
blktests-ci
bot
force-pushed
the
linus-master_base
branch
from
40967f0 to
d4e9bad
Compare
Author
|
Upstream branch: af4e9ef |
blktests-ci
bot
force-pushed
the
series/1056653=>linus-master
branch
from
b689ffa to
800339e
Compare
blktests-ci
bot
force-pushed
the
linus-master_base
branch
from
d4e9bad to
ecd10e2
Compare
Author
|
Upstream branch: af4e9ef |
blktests-ci
bot
force-pushed
the
linus-master_base
branch
from
ecd10e2 to
d0e1bed
Compare
blktests-ci
bot
force-pushed
the
series/1056653=>linus-master
branch
from
800339e to
9202378
Compare
blktests-ci
bot
force-pushed
the
linus-master_base
branch
from
d0e1bed to
6b51c57
Compare
Author
|
Upstream branch: 0031c06 |
blktests-ci
bot
force-pushed
the
series/1056653=>linus-master
branch
from
9202378 to
0183668
Compare
blktests-ci
bot
force-pushed
the
linus-master_base
branch
from
6b51c57 to
78036b2
Compare
Author
|
Upstream branch: ecc64d2 |
blktests-ci
bot
force-pushed
the
series/1056653=>linus-master
branch
from
0183668 to
7c7eab7
Compare
blktests-ci
bot
force-pushed
the
linus-master_base
branch
from
78036b2 to
bbb3394
Compare
Author
|
Upstream branch: c107785 |
blktests-ci
bot
force-pushed
the
series/1056653=>linus-master
branch
from
7c7eab7 to
6de080f
Compare
blktests-ci
bot
force-pushed
the
linus-master_base
branch
from
bbb3394 to
901a429
Compare
Author
|
Upstream branch: 5ee8dbf |
blktests-ci
bot
force-pushed
the
series/1056653=>linus-master
branch
from
6de080f to
00c1d08
Compare
blktests-ci
bot
force-pushed
the
linus-master_base
branch
from
901a429 to
1f19ba6
Compare
Author
|
Upstream branch: 1f318b9 |
blktests-ci
bot
force-pushed
the
series/1056653=>linus-master
branch
from
00c1d08 to
b87ce81
Compare
blktests-ci
bot
force-pushed
the
linus-master_base
branch
from
1f19ba6 to
e79276a
Compare
A bio segment may have partial interval block data with the rest continuing into the next segments because direct-io data payloads only need to align in memory to the device's DMA limits. At the same time, the protection information may also be split in multiple segments. The most likely way that may happen is if two requests merge, or if we're directly using the io_uring user metadata. The generate/verify, however, only ever accessed the first bip_vec. Further, it may be possible to unalign the protection fields from the user space buffer, or if there are odd additional opaque bytes in front or in back of the protection information metadata region. Change up the iteration to allow spanning multiple segments. This patch is mostly a re-write of the protection information handling to allow any arbitrary alignments, so it's probably easier to review the end result rather than the diff. Many controllers are not able to handle interval data composed of multiple segments when PI is used, so this patch introduces a new integrity limit that a low level driver can set to notify that it is capable, default to false. The nvme driver is the first one to enable it in this patch. Everyone else will force DMA alignment to the logical block size as before to ensure interval data is always aligned within a single segment. Reviewed-by: "Martin K. Petersen" <martin.petersen@oracle.com> Reviewed-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Keith Busch <kbusch@kernel.org>
Author
|
Upstream branch: None |
blktests-ci
bot
force-pushed
the
series/1056653=>linus-master
branch
from
b87ce81 to
259c252
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull request for series with
subject: blk-integrity: support arbitrary buffer alignment
version: 1
url: https://patchwork.kernel.org/project/linux-block/list/?series=1056653