linux/drivers/block/drbd/drbd_req.c, branch v3.2.7

block: remove support for bio remapping from ->make_request

2011-09-12T10:12:01Z

There is very little benefit in allowing to let a ->make_request instance update the bios device and sector and loop around it in __generic_make_request when we can archive the same through calling generic_make_request from the driver and letting the loop in generic_make_request handle it. Note that various drivers got the return value from ->make_request and returned non-zero values for errors. Signed-off-by: Christoph Hellwig Acked-by: NeilBrown Signed-off-by: Jens Axboe

drbd: Fix spelling

2011-05-24T08:21:29Z

Found these with the help of ispell -l. Signed-off-by: Bart Van Assche Signed-off-by: Lars Ellenberg Signed-off-by: Philipp Reisner

drbd: fix potential activity log refcount imbalance in error path

2011-05-24T08:06:44Z

It is no longer sufficient to trigger on local WRITE, we need to check on (rq_state & RQ_IN_ACT_LOG) before calling drbd_al_complete_io also in the error path. Signed-off-by: Philipp Reisner Signed-off-by: Lars Ellenberg

drbd: drop code present under #ifdef which is relevant to 2.6.28 and below

2011-03-10T10:48:21Z

Signed-off-by: Or Gerlitz Signed-off-by: Philipp Reisner Signed-off-by: Lars Ellenberg

drbd: Implemented real timeout checking for request processing time

2011-03-10T10:48:16Z

Signed-off-by: Philipp Reisner Signed-off-by: Lars Ellenberg

drbd: Removed left over, now wrong comments

2011-03-10T10:48:09Z

Signed-off-by: Philipp Reisner Signed-off-by: Lars Ellenberg

drbd: fix potential imbalance of ap_in_flight

2011-03-10T10:48:06Z

When we receive a barrier ack, we walk the ring list of drbd requests in the transfer log of the respective epoch, do some housekeeping, and free those objects. We tried to keep epochs of mirrored and unmirrored drbd requests separate, and assert that no local-only requests are present in a barrier_acked epoch. It turns out that this has quite a number of corner cases and would add bloated code without functional benefit. We now revert the (insufficient) commits drbd: Fixed an issue with AHEAD -> SYNC_SOURCE transitions drbd: Ensure that an epoch contains only requests of one kind and instead fix the processing of barrier acks to cope with a mix of local-only and mirrored requests. Signed-off-by: Philipp Reisner Signed-off-by: Lars Ellenberg

drbd: Ensure that an epoch contains only requests of one kind

2011-03-10T10:45:42Z

The assert in drbd_req.c:755 forces us to have only requests of one kind in an epoch. The two kinds we distinguish here are: local-only or mirrored. Signed-off-by: Philipp Reisner Signed-off-by: Lars Ellenberg

drbd: Nothing should stop SyncSource -> Ahead transitions

2011-03-10T10:45:34Z

Signed-off-by: Philipp Reisner Signed-off-by: Lars Ellenberg

drbd: Be more careful with SyncSource -> Ahead transitions

2011-03-10T10:45:26Z

We may not get from SyncSource to Ahead if we have sent some P_RS_DATA_REPLY packets to the peer and are waiting for P_WRITE_ACK. Again, this is not relevant for proper tuned systems, but makes sure that the not-tuned system does not get diverging bitmaps. Signed-off-by: Philipp Reisner Signed-off-by: Lars Ellenberg