From: Joel Granados <joel.granados@kernel.org>
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: netdev@vger.kernel.org, stable@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
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>,
Randy Dunlap <rdunlap@infradead.org>,
David Ahern <dsahern@kernel.org>,
Ido Schimmel <idosch@nvidia.com>,
Thomas Gleixner <tglx@kernel.org>,
Petr Pavlu <petr.pavlu@suse.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
Fernando Fernandez Mancera <fmancera@suse.de>,
Willem de Bruijn <willemb@google.com>,
Maoyi Xie <maoyi.xie@ntu.edu.sg>,
Gerd Rausch <gerd.rausch@oracle.com>,
Zhan Xusheng <zhanxusheng1024@gmail.com>,
Oleg Nesterov <oleg@redhat.com>,
Chia-Yu Chang <chia-yu.chang@nokia-bell-labs.com>,
Yung Chih Su <yuuchihsu@gmail.com>,
Wyatt Feng <bronzed_45_vested@icloud.com>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
Flavio Leitner <fbl@redhat.com>, Petr Mladek <pmladek@suse.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2 5/5] net: restrict message_cost and message_burst to non-negative values
Date: Tue, 3 Nov 2026 09:00:18 +0100 [thread overview]
Message-ID: <aumTvqiaDRTd9rlY@hobbes> (raw)
In-Reply-To: <20261027104701.296240-6-jiayuan.chen@linux.dev>
[-- Attachment #1: Type: text/plain, Size: 6427 bytes --]
On Tue, Oct 27, 2026 at 06:45:33PM +0800, Jiayuan Chen wrote:
> net.core.message_cost and net.core.message_burst feed the interval and
> burst of net_ratelimit_state, but neither rejects negative values:
> message_burst uses plain proc_dointvec, and message_cost uses
> proc_dointvec_jiffies, which happily stores -1 second as -HZ jiffies.
>
> Since commit a940d145cc38 ("ratelimit: Warn if ->interval or ->burst are
> negative"), ___ratelimit() splats on such values, so the next
> net_ratelimit() caller warns, e.g. a martian source log:
>
> Negative interval (-250) or burst (10): Uninitialized ratelimit_state structure?
> WARNING: lib/ratelimit.c:43 at ___ratelimit+0x56e/0x960, CPU#1: ping/3218
> RIP: 0010:___ratelimit+0x578/0x960
> Call Trace:
> <IRQ>
> net_ratelimit+0x1c/0x30
> ip_handle_martian_source+0x1bb/0x340
> ip_route_input_slow+0x1057/0x3650
> ip_route_input_noref+0x104/0x260
> arp_process+0x109b/0x2510
> arp_rcv+0x381/0x460
> __netif_receive_skb_one_core+0x173/0x1c0
> __netif_receive_skb+0x21/0x150
> process_backlog+0x37e/0x1200
> __napi_poll.constprop.0+0xa5/0x5e0
> net_rx_action+0x4c0/0xf70
> handle_softirqs+0x204/0x9b0
> __do_softirq+0x10/0x18
> do_softirq.part.0+0x49/0xd0
> </IRQ>
>
> Negative values never meant anything here: 0 already expresses both
> "no limit" (interval) and "suppress everything" (burst).
>
> Reject them at write time. message_burst can simply use
> proc_dointvec_minmax with extra1 = 0. proc_dointvec_jiffies has no
> minmax variant, so add proc_dointvec_jiffies_minmax(), mirroring
> proc_dointvec_ms_jiffies_minmax(), and use it for message_cost with
> extra1 = 0. Note that like the ms variant, extra1/extra2 are compared
> against the converted jiffies value.
>
> Fixes: a940d145cc38 ("ratelimit: Warn if ->interval or ->burst are negative")
> Cc: stable@vger.kernel.org
> Suggested-by: Joel Granados <joel.granados@kernel.org>
> Signed-off-by: Jiayuan Chen <jiayuan.chen@linux.dev>
> ---
> include/linux/jiffies.h | 2 ++
> kernel/time/jiffies.c | 40 ++++++++++++++++++++++++++++++++++++++
> net/core/sysctl_net_core.c | 6 ++++--
> 3 files changed, 46 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/jiffies.h b/include/linux/jiffies.h
> index bbd57061802cd..de12920f8e94b 100644
> --- a/include/linux/jiffies.h
> +++ b/include/linux/jiffies.h
> @@ -646,6 +646,8 @@ extern unsigned long nsecs_to_jiffies(u64 n);
> struct ctl_table;
> int proc_dointvec_jiffies(const struct ctl_table *table, int dir, void *buffer,
> size_t *lenp, loff_t *ppos);
> +int proc_dointvec_jiffies_minmax(const struct ctl_table *table, int dir,
> + void *buffer, size_t *lenp, loff_t *ppos);
> int proc_dointvec_ms_jiffies_minmax(const struct ctl_table *table, int dir,
> void *buffer, size_t *lenp, loff_t *ppos);
> int proc_dointvec_userhz_jiffies(const struct ctl_table *table, int dir,
> diff --git a/kernel/time/jiffies.c b/kernel/time/jiffies.c
> index 9b3487d40cd6a..22a70caa58bc1 100644
> --- a/kernel/time/jiffies.c
> +++ b/kernel/time/jiffies.c
> @@ -165,6 +165,14 @@ static int do_proc_int_conv_jiffies(bool *negp, ulong *u_ptr, int *k_ptr,
> sysctl_u2k_int_conv_hz, sysctl_k2u_int_conv_hz);
> }
>
> +static int do_proc_int_conv_jiffies_minmax(bool *negp, ulong *u_ptr,
> + int *k_ptr, int dir,
> + const struct ctl_table *tbl)
> +{
> + return proc_int_conv(negp, u_ptr, k_ptr, dir, tbl, true,
> + sysctl_u2k_int_conv_hz, sysctl_k2u_int_conv_hz);
> +}
> +
> static int do_proc_int_conv_userhz_jiffies(bool *negp, ulong *u_ptr,
> int *k_ptr, int dir,
> const struct ctl_table *tbl)
> @@ -213,6 +221,13 @@ static int do_proc_int_conv_jiffies(bool *negp, ulong *u_ptr, int *k_ptr,
> return -ENOSYS;
> }
>
> +static int do_proc_int_conv_jiffies_minmax(bool *negp, ulong *u_ptr,
> + int *k_ptr, int dir,
> + const struct ctl_table *tbl)
> +{
> + return -ENOSYS;
> +}
> +
> static int do_proc_int_conv_userhz_jiffies(bool *negp, ulong *u_ptr,
> int *k_ptr, int dir,
> const struct ctl_table *tbl)
> @@ -263,6 +278,31 @@ int proc_dointvec_jiffies(const struct ctl_table *table, int dir,
> }
> EXPORT_SYMBOL(proc_dointvec_jiffies);
>
> +/**
> + * proc_dointvec_jiffies_minmax - read a vector of integers as seconds with min/max values
> + * @table: the sysctl table
> + * @dir: %TRUE if this is a write to the sysctl file
> + * @buffer: the user buffer
> + * @lenp: the size of the user buffer
> + * @ppos: file position
> + *
> + * Reads/writes up to table->maxlen/sizeof(unsigned int) integer
> + * values from/to the user buffer, treated as an ASCII string.
> + * The values read are assumed to be in seconds, and are converted into
> + * jiffies. The converted values are checked against the optional
> + * table->extra1 (min) and table->extra2 (max) bounds, in jiffies;
> + * a value outside the range is rejected with -EINVAL.
> + *
> + * Returns 0 on success.
> + */
> +int proc_dointvec_jiffies_minmax(const struct ctl_table *table, int dir,
> + void *buffer, size_t *lenp, loff_t *ppos)
> +{
> + return proc_dointvec_conv(table, dir, buffer, lenp, ppos,
> + do_proc_int_conv_jiffies_minmax);
> +}
> +EXPORT_SYMBOL(proc_dointvec_jiffies_minmax);
> +
> /**
> * proc_dointvec_userhz_jiffies - read a vector of integers as 1/USER_HZ seconds
> * @table: the sysctl table
> diff --git a/net/core/sysctl_net_core.c b/net/core/sysctl_net_core.c
> index 473c162736d69..9226b96f2e89b 100644
> --- a/net/core/sysctl_net_core.c
> +++ b/net/core/sysctl_net_core.c
> @@ -544,14 +544,16 @@ static struct ctl_table net_core_table[] = {
> .data = &net_ratelimit_state.interval,
> .maxlen = sizeof(int),
> .mode = 0644,
> - .proc_handler = proc_dointvec_jiffies,
> + .proc_handler = proc_dointvec_jiffies_minmax,
> + .extra1 = SYSCTL_ZERO,
> },
> {
> .procname = "message_burst",
> .data = &net_ratelimit_state.burst,
> .maxlen = sizeof(int),
> .mode = 0644,
> - .proc_handler = proc_dointvec,
> + .proc_handler = proc_dointvec_minmax,
> + .extra1 = SYSCTL_ZERO,
> },
> #ifdef CONFIG_RPS
> {
> --
> 2.43.0
>
This LGTM
Reviewed-by: Joel Granados <joel.granados@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2026-11-03 8:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 10:45 [PATCH net v2 0/5] net: fix misc signed overflows caused by bad sysctl values Jiayuan Chen
2026-10-27 10:45 ` [PATCH net v2 1/5] ipv6: restrict gc_elasticity to 31 Jiayuan Chen
2026-10-28 23:58 ` Kuniyuki Iwashima
2026-10-29 1:46 ` Jiayuan Chen
2026-10-29 1:53 ` Kuniyuki Iwashima
2026-10-29 2:07 ` Jiayuan Chen
2026-10-27 10:45 ` [PATCH net v2 2/5] ipv4: fix shift-out-of-bounds in ip_rt_send_redirect() Jiayuan Chen
2026-10-27 11:54 ` Fernando Fernandez Mancera
2026-10-27 10:45 ` [PATCH net v2 3/5] ipv6: restrict mld_qrv to 255 Jiayuan Chen
2026-10-27 10:45 ` [PATCH net v2 4/5] ipv4: restrict igmp_qrv " Jiayuan Chen
2026-10-27 10:45 ` [PATCH net v2 5/5] net: restrict message_cost and message_burst to non-negative values Jiayuan Chen
2026-10-27 11:56 ` Fernando Fernandez Mancera
2026-10-28 23:07 ` Jakub Kicinski
2026-11-03 8:00 ` Joel Granados [this message]
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=aumTvqiaDRTd9rlY@hobbes \
--to=joel.granados@kernel.org \
--cc=bronzed_45_vested@icloud.com \
--cc=chia-yu.chang@nokia-bell-labs.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=fbl@redhat.com \
--cc=fmancera@suse.de \
--cc=gerd.rausch@oracle.com \
--cc=hannes@stressinduktion.org \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=jiayuan.chen@linux.dev \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maoyi.xie@ntu.edu.sg \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=pabeni@redhat.com \
--cc=paulmck@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=pmladek@suse.com \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=tglx@kernel.org \
--cc=willemb@google.com \
--cc=yuuchihsu@gmail.com \
--cc=zhanxusheng1024@gmail.com \
/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
all inboxes | Powered by JetHome®