From: Mark Rutland <mark.rutland@arm.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E . McKenney" <paulmck@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>,
"H . Peter Anvin" <hpa@zytor.com>, Paul Turner <pjt@google.com>,
linux-api@vger.kernel.org, Peter Oskolkov <posk@posk.io>
Subject: Re: [RFC PATCH] rseq: Use pr_warn_once() when deprecated/unknown ABI flags are encountered
Date: Thu, 29 Sep 2022 17:06:40 +0100 [thread overview]
Message-ID: <YzXCkDJg8vEYqwJH@FVFF77S0Q05N> (raw)
In-Reply-To: <20220929141227.205343-1-mathieu.desnoyers@efficios.com>
On Thu, Sep 29, 2022 at 10:12:27AM -0400, Mathieu Desnoyers wrote:
> These commits use WARN_ON_ONCE() and kill the offending processes when
> deprecated and unknown flags are encountered:
>
> commit c17a6ff93213 ("rseq: Kill process when unknown flags are encountered in ABI structures")
> commit 0190e4198e47 ("rseq: Deprecate RSEQ_CS_FLAG_NO_RESTART_ON_* flags")
>
> The WARN_ON_ONCE() triggered by userspace input prevents use of
> Syzkaller to fuzz the rseq system call.
>
> Replace this WARN_ON_ONCE() by pr_warn_once() messages which contain
> actually useful information.
>
> Reported-by: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Thanks for this!
I've set off a Syzkaller run with this applied, and I'll be able to tell you in
a day or two whether that's made it possible to spot anything more interesting.
Regardless, I think this is a good change, so FWIW:
Acked-by: Mark Rutland <mark.rutland@arm.com>
Mark.
> ---
> kernel/rseq.c | 19 +++++++++++++++++--
> 1 file changed, 17 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/rseq.c b/kernel/rseq.c
> index bda8175f8f99..d38ab944105d 100644
> --- a/kernel/rseq.c
> +++ b/kernel/rseq.c
> @@ -171,12 +171,27 @@ static int rseq_get_rseq_cs(struct task_struct *t, struct rseq_cs *rseq_cs)
> return 0;
> }
>
> +static bool rseq_warn_flags(const char *str, u32 flags)
> +{
> + u32 test_flags;
> +
> + if (!flags)
> + return false;
> + test_flags = flags & RSEQ_CS_NO_RESTART_FLAGS;
> + if (test_flags)
> + pr_warn_once("Deprecated flags (%u) in %s ABI structure", test_flags, str);
> + test_flags = flags & ~RSEQ_CS_NO_RESTART_FLAGS;
> + if (test_flags)
> + pr_warn_once("Unknown flags (%u) in %s ABI structure", test_flags, str);
> + return true;
> +}
> +
> static int rseq_need_restart(struct task_struct *t, u32 cs_flags)
> {
> u32 flags, event_mask;
> int ret;
>
> - if (WARN_ON_ONCE(cs_flags & RSEQ_CS_NO_RESTART_FLAGS) || cs_flags)
> + if (rseq_warn_flags("rseq_cs", cs_flags))
> return -EINVAL;
>
> /* Get thread flags. */
> @@ -184,7 +199,7 @@ static int rseq_need_restart(struct task_struct *t, u32 cs_flags)
> if (ret)
> return ret;
>
> - if (WARN_ON_ONCE(flags & RSEQ_CS_NO_RESTART_FLAGS) || flags)
> + if (rseq_warn_flags("rseq", flags))
> return -EINVAL;
>
> /*
> --
> 2.30.2
>
next prev parent reply other threads:[~2022-09-29 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 14:12 [RFC PATCH] rseq: Use pr_warn_once() when deprecated/unknown ABI flags are encountered Mathieu Desnoyers
2022-09-29 16:06 ` Mark Rutland [this message]
2022-09-29 16:11 ` Paul E. McKenney
2022-10-21 2:11 ` Mathieu Desnoyers
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=YzXCkDJg8vEYqwJH@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=boqun.feng@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=posk@posk.io \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).