From: Frederic Weisbecker <frederic@kernel.org>
To: Sergey Shtylyov <s.shtylyov@auroraos.dev>
Cc: Anna-Maria Behnsen <anna-maria@linutronix.de>,
Ingo Molnar <mingo@kernel.org>, Thomas Gleixner <tglx@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tick/sched: check skew_tick kernel parameter's validity
Date: Tue, 1 Sep 2026 14:55:55 +0200 [thread overview]
Message-ID: <apbLW_Y1CScaZoR7@localhost.localdomain> (raw)
In-Reply-To: <20260829202535.46470-1-s.shtylyov@auroraos.dev>
Hi,
Le Sat, Aug 29, 2026 at 11:25:35PM +0300, Sergey Shtylyov a écrit :
> In skew_tick(), the result of get_option() call is ignored, so even if a
> value of the skew_tick kernel parameter was not specified (or specified
> as a list or range), the kernel won't complain. Add the missing check...
>
> Found by Linux Verification Center (linuxtesting.org) with the Svace static
> analysis tool.
>
> Signed-off-by: Sergey Shtylyov <s.shtylyov@auroraos.dev>
>
> ---
> The patch is against the timers/nohz branch of the tip.git repo...
>
> kernel/time/tick-sched.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
> index c1ee0b256445..34ceccdd49b5 100644
> --- a/kernel/time/tick-sched.c
> +++ b/kernel/time/tick-sched.c
> @@ -1483,7 +1483,8 @@ static int sched_skew_tick;
>
> static int __init skew_tick(char *str)
> {
> - get_option(&str, &sched_skew_tick);
> + if (get_option(&str, &sched_skew_tick) != 1)
> + return -EINVAL;
>
> return 0;
I'm not sure that matters. Initcall return values seem to be ignored on boot.
Looks like only modules do care.
Thanks.
> }
> --
> 2.55.0
--
Frederic Weisbecker
SUSE Labs
next prev parent reply other threads:[~2026-09-01 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 20:25 Sergey Shtylyov
2026-09-01 12:55 ` Frederic Weisbecker [this message]
2026-09-01 17:43 ` Sergey Shtylyov
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=apbLW_Y1CScaZoR7@localhost.localdomain \
--to=frederic@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=s.shtylyov@auroraos.dev \
--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
all inboxes | Powered by JetHome®