-
Notifications
You must be signed in to change notification settings - Fork 0
drbd: always set BLK_FEAT_STABLE_WRITES #547
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: f14faaf |
|
Upstream branch: f14faaf |
de8ac99 to
c7e8199
Compare
7c2ae0a to
54294d6
Compare
|
Upstream branch: b7ff715 |
c7e8199 to
2140b96
Compare
54294d6 to
eb49f7b
Compare
|
Upstream branch: e7aa572 |
2140b96 to
252a8ea
Compare
eb49f7b to
30e5c22
Compare
|
Upstream branch: 05f7e89 |
DRBD requires stable pages because it may read the same bio data multiple times for local disk I/O and network transmission, and in some cases for calculating checksums. The BLK_FEAT_STABLE_WRITES flag is set when the device is first created, but blk_set_stacking_limits() clears it whenever a backing device is attached. In some cases the flag may be inherited from the backing device, but we want it to be enabled at all times. Unconditionally re-enable BLK_FEAT_STABLE_WRITES in drbd_reconsider_queue_parameters() after the queue parameter negotiations. Also, document why we want this flag enabled in the first place. Fixes: 1a02f3a ("block: move the stable_writes flag to queue_limits") Signed-off-by: Christoph Böhmwalder <[email protected]> Reviewed-by: Christoph Hellwig <[email protected]>
252a8ea to
59bb28c
Compare
Pull request for series with
subject: drbd: always set BLK_FEAT_STABLE_WRITES
version: 1
url: https://patchwork.kernel.org/project/linux-block/list/?series=1051265