lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 3 Sep 2014 15:02:36 +0200 From: Imre Palik <imrep.amz@...il.com> To: drbd-dev@...ts.linbit.com Cc: Philipp Reisner <philipp.reisner@...bit.com>, Lars Ellenberg <lars.ellenberg@...bit.com>, linux-kernel@...r.kernel.org, "Palik, Imre" <imrep@...zon.de>, Matt Wilson <msw@...zon.com> Subject: [PATCH] drbd: fix throttling on newly created DM backing devices From: "Palik, Imre" <imrep@...zon.de> If the drbd backing device is a new device mapper device (e.g., a dm-linear mapping of an existing block device that contains data), the counters are initially 0 even though the device contains useful data. This causes throttling until something accesses the drbd device or the backing device. The patch disables throttling, as long as only resync is responsible for disk activity on a freshly created device. Reported-by: Mikhail Sugakov <msugakov@...zon.de> Cc: Matt Wilson <msw@...zon.com> Signed-off-by: Imre Palik <imrep@...zon.de> --- drivers/block/drbd/drbd_receiver.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/block/drbd/drbd_receiver.c b/drivers/block/drbd/drbd_receiver.c index 9342b8d..511d2eb 100644 --- a/drivers/block/drbd/drbd_receiver.c +++ b/drivers/block/drbd/drbd_receiver.c @@ -2482,7 +2482,8 @@ bool drbd_rs_c_min_rate_throttle(struct drbd_device *device) atomic_read(&device->rs_sect_ev); if (atomic_read(&device->ap_actlog_cnt) - || !device->rs_last_events || curr_events - device->rs_last_events > 64) { + || (curr_events && (!device->rs_last_events + || curr_events - device->rs_last_events > 64))) { unsigned long rs_left; int i; -- 1.7.9.5 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists