Linux filesystem development
 help / color / mirror / Atom feed
From: Kuniyuki Iwashima <kuniyu@google.com>
To: Kees Cook <kees@kernel.org>,
	Joel Granados <joel.granados@kernel.org>,
	 Thomas Gleixner <tglx@kernel.org>
Cc: Kuniyuki Iwashima <kuniyu@google.com>,
	Kuniyuki Iwashima <kuni1840@gmail.com>,
	linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/2] sysctl: Restore minmax check for proc_do{int,ulong}vec_ms_jiffies_minmax().
Date: Sat,  5 Sep 2026 23:36:29 +0000	[thread overview]
Message-ID: <20260905233819.1064529-1-kuniyu@google.com> (raw)

The recent refactoring accidentally removed the minmax
check from proc_dointvec_ms_jiffies_minmax() and
proc_doulongvec_ms_jiffies_minmax().

The series restores the validation, and patch 2 adds
the INT_MAX limit for proc_doulongvec_ms_jiffies_minmax()
to avoid silent truncation.


Kuniyuki Iwashima (2):
  sysctl: Make proc_dointvec_ms_jiffies_minmax() enforce minmax again.
  sysctl: Make proc_doulongvec_ms_jiffies_minmax() enforce minmax again.

 kernel/time/jiffies.c | 17 ++++++++++-------
 1 file changed, 10 insertions(+), 7 deletions(-)

-- 
2.55.0.1003.g10538fe699-goog


             reply	other threads:[~2026-09-05 23:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-05 23:36 Kuniyuki Iwashima [this message]
2026-09-05 23:36 ` [PATCH 1/2] sysctl: Make proc_dointvec_ms_jiffies_minmax() enforce minmax again Kuniyuki Iwashima
2026-09-08 11:06   ` Joel Granados
2026-09-08 18:38     ` Kuniyuki Iwashima
2026-09-09 13:48       ` Joel Granados
2026-09-05 23:36 ` [PATCH 2/2] sysctl: Make proc_doulongvec_ms_jiffies_minmax() " Kuniyuki Iwashima
2026-09-08 12:15   ` Joel Granados
2026-09-08 18:44     ` Kuniyuki Iwashima
2026-09-09 13:44       ` Joel Granados
2026-09-09 17:07         ` Kuniyuki Iwashima
2026-09-10  9:04           ` Joel Granados
2026-09-10 10:45             ` Joel Granados
2026-09-10 16:43               ` Kuniyuki Iwashima

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=20260905233819.1064529-1-kuniyu@google.com \
    --to=kuniyu@google.com \
    --cc=joel.granados@kernel.org \
    --cc=kees@kernel.org \
    --cc=kuni1840@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=tglx@kernel.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