-
Notifications
You must be signed in to change notification settings - Fork 0
fs: remove power of 2 and length boundary atomic write restrictions #428
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: linus-master_base
Are you sure you want to change the base?
Conversation
|
Upstream branch: d26143b |
4a5ddea to
0ab4e8c
Compare
|
Upstream branch: aacb0a6 |
419aeb1 to
044a840
Compare
0ab4e8c to
a2a6d78
Compare
|
Upstream branch: aacb0a6 |
044a840 to
5f727d0
Compare
a2a6d78 to
f962a4d
Compare
|
Upstream branch: 623fb99 |
5f727d0 to
3ee3ffd
Compare
f962a4d to
06634b5
Compare
|
Upstream branch: b543459 |
3ee3ffd to
6fa4679
Compare
06634b5 to
8a473ad
Compare
|
Upstream branch: 944aacb |
generic_atomic_write_valid() returns EINVAL for non-power-of-2 and for non-length-aligned writes. This check is used for block devices, ext4 and xfs, but neither ext4 nor xfs rely on power of 2 restrictions. For block devices, neither NVMe nor SCSI specification doesn't require length alignment and 2^N length. Both specifications only require to respect the atomic write boundary if it's set (NABSPF/NABO for NVMe and ATOMIC BOUNDARY for SCSI). NVMe subsystem already checks writes against this boundary; SCSI uses an explicit atomic write command so the write is checked by the drive itself. Signed-off-by: Vitaliy Filippov <vitalifster@gmail.com>
6fa4679 to
6cbc824
Compare
Pull request for series with
subject: fs: remove power of 2 and length boundary atomic write restrictions
version: 1
url: https://patchwork.kernel.org/project/linux-block/list/?series=1036389