From: Breno Leitao <leitao@debian.org>
To: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Shuah Khan <shuah@kernel.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
paulmck@kernel.org, gustavold@gmail.com, asantostc@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org,
Breno Leitao <leitao@debian.org>,
kernel-team@meta.com
Subject: [PATCH net-next v3 3/5] netconsole: allow configuring the rate limit interval through configfs
Date: Mon, 14 Sep 2026 05:09:53 -0700 [thread overview]
Message-ID: <20260914-netcons_ratelimit-v3-3-8e81b789ab37@debian.org> (raw)
In-Reply-To: <20260914-netcons_ratelimit-v3-0-8e81b789ab37@debian.org>
The per-target token bucket has no interface, so every target is still
unlimited.
Expose the interval as ratelimit_interval_ms through configfs. It
defaults to zero, so a target stays unlimited until an administrator
sets one.
The write restarts the interval instead of only publishing the new
value. A target is configured while it floods, by which point the
bucket is empty, and ___ratelimit() only refills it once the interval
it was set with has elapsed.
Reject more than INT_MAX milliseconds. msecs_to_jiffies() saturates at
MAX_JIFFY_OFFSET, which is below INT_MAX on 32-bit, so checking only
the jiffies value would take a write there that a 64-bit kernel turns
down.
Signed-off-by: Breno Leitao <leitao@debian.org>
---
drivers/net/netconsole.c | 39 +++++++++++++++++++++++++++++++++++++++
1 file changed, 39 insertions(+)
diff --git a/drivers/net/netconsole.c b/drivers/net/netconsole.c
index c1c92413c0a5c5..d4e3ac272e9b4a 100644
--- a/drivers/net/netconsole.c
+++ b/drivers/net/netconsole.c
@@ -958,6 +958,14 @@ static ssize_t transmit_errors_show(struct config_item *item, char *buf)
return sysfs_emit(buf, "%llu\n", xmit_drop_count + enomem_count);
}
+static ssize_t ratelimit_interval_ms_show(struct config_item *item, char *buf)
+{
+ struct netconsole_target *nt = to_target(item);
+
+ return sysfs_emit(buf, "%u\n",
+ jiffies_to_msecs(READ_ONCE(nt->ratelimit.interval)));
+}
+
/* configfs helper to display if cpu_nr sysdata feature is enabled */
static ssize_t sysdata_cpu_nr_enabled_show(struct config_item *item, char *buf)
{
@@ -1353,6 +1361,35 @@ static ssize_t remote_mac_store(struct config_item *item, const char *buf,
return ret;
}
+static ssize_t ratelimit_interval_ms_store(struct config_item *item,
+ const char *buf, size_t count)
+{
+ struct netconsole_target *nt = to_target(item);
+ unsigned int interval;
+ unsigned long jifs;
+ ssize_t ret;
+
+ ret = kstrtouint(buf, 10, &interval);
+ if (ret)
+ return ret;
+
+ /* msecs_to_jiffies() saturates below INT_MAX on 32-bit, so the
+ * jiffies value alone does not bound what userspace wrote.
+ */
+ jifs = msecs_to_jiffies(interval);
+ if (interval > INT_MAX || jifs > INT_MAX)
+ return -ERANGE;
+
+ /* Restart the interval, so a target that is already flooding picks
+ * the new limit up now rather than at the next refill.
+ */
+ dynamic_netconsole_mutex_lock();
+ ratelimit_state_reset_interval(&nt->ratelimit, jifs);
+ dynamic_netconsole_mutex_unlock();
+
+ return count;
+}
+
struct userdatum {
struct config_item item;
char value[MAX_EXTRADATA_VALUE_LEN];
@@ -1717,6 +1754,7 @@ CONFIGFS_ATTR_RO(, local_mac);
CONFIGFS_ATTR(, remote_mac);
CONFIGFS_ATTR(, release);
CONFIGFS_ATTR_RO(, transmit_errors);
+CONFIGFS_ATTR(, ratelimit_interval_ms);
static struct configfs_attribute *netconsole_target_attrs[] = {
&attr_enabled,
@@ -1730,6 +1768,7 @@ static struct configfs_attribute *netconsole_target_attrs[] = {
&attr_local_mac,
&attr_remote_mac,
&attr_transmit_errors,
+ &attr_ratelimit_interval_ms,
NULL,
};
--
2.53.0-Meta
next prev parent reply other threads:[~2026-09-14 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 12:09 [PATCH net-next v3 0/5] netconsole: Support messages ratelimit-ing Breno Leitao
2026-09-14 12:09 ` [PATCH net-next v3 1/5] netconsole: send the oops when oops_only is set Breno Leitao
2026-09-23 15:38 ` Gustavo Luiz Duarte
2026-09-14 12:09 ` [PATCH net-next v3 2/5] netconsole: add a per-target message rate limit Breno Leitao
2026-09-23 15:38 ` Gustavo Luiz Duarte
2026-09-14 12:09 ` Breno Leitao [this message]
2026-09-23 15:39 ` [PATCH net-next v3 3/5] netconsole: allow configuring the rate limit interval through configfs Gustavo Luiz Duarte
2026-09-14 12:09 ` [PATCH net-next v3 4/5] netconsole: allow configuring the rate limit burst " Breno Leitao
2026-09-23 15:39 ` Gustavo Luiz Duarte
2026-09-14 12:09 ` [PATCH net-next v3 5/5] docs: netconsole: document rate limit feature Breno Leitao
2026-09-23 15:40 ` Gustavo Luiz Duarte
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260914-netcons_ratelimit-v3-3-8e81b789ab37@debian.org \
--to=leitao@debian.org \
--cc=andrew+netdev@lunn.ch \
--cc=asantostc@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gustavold@gmail.com \
--cc=horms@kernel.org \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paulmck@kernel.org \
--cc=rdunlap@infradead.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox