FAILED: patch "[PATCH] dm: fix printk() rate limiting code" failed to apply to 4.12-stable tree
Subsystems (2)
[email protected]
maintainerThe patch below does not apply to the 4.12-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
Quoted 1 line
From
604407890ecf624c2fb41013c82b22aade59b455Mon Sep 17 00:00:00 2001
From: Bart Van Assche <[email protected]>
Date: Wed, 9 Aug 2017 11:32:11 -0700
Subject: [PATCH] dm: fix printk() rate limiting code
Using the same rate limiting state for different kinds of messages is wrong because this can cause a high frequency message to suppress a report of a low frequency message. Hence use a unique rate limiting state per message type.
drivers/md/dm.c +0 -10
@@ -27,16 +27,6 @@#define DM_MSG_PREFIX "core" -#ifdef CONFIG_PRINTK -/* -* ratelimit state to be used in DMXXX_LIMIT(). -*/ -DEFINE_RATELIMIT_STATE (dm_ratelimit_state, -DEFAULT_RATELIMIT_INTERVAL , -DEFAULT_RATELIMIT_BURST ); -EXPORT_SYMBOL (dm_ratelimit_state); -#endif -/* * Cookies are numeric values sent with CHANGE and REMOVE * uevents while resuming, removing or renaming the device.
include/linux/device-mapper.h +12 -29
58 lines not on this page · raw message