From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Peter Zijlstra <peterz@infradead.org>, Ingo Molnar <mingo@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH for sched/core] rseq: Fix rseq unregistration
Date: Mon, 20 Jan 2025 11:49:14 -0500 [thread overview]
Message-ID: <525f88ba-b082-4744-b54a-a23a264fb8a3@efficios.com> (raw)
In-Reply-To: <20250116205956.836074-1-mathieu.desnoyers@efficios.com>
On 2025-01-16 15:59, Mathieu Desnoyers wrote:
> A logic inversion in rseq_reset_rseq_cpu_node_id() causes the rseq
> unregistration to fail when rseq_validate_ro_fields() succeeds rather
> than the opposite.
>
> This affects both CONFIG_DEBUG_RSEQ=y and CONFIG_DEBUG_RSEQ=n.
>
> Fixes: 7d5265ffcd8b ("rseq: Validate read-only fields under DEBUG_RSEQ config")
> Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
Ingo, Peter, this fix should have been part of the PR sent to Linus
earlier today [1]. Otherwise rseq unregistration is broken.
Thanks,
Mathieu
[1] https://lore.kernel.org/lkml/Z44ufdYZWaM50kxF@gmail.com/
> ---
> kernel/rseq.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/rseq.c b/kernel/rseq.c
> index e04bb30a2eb8..442aba29bc4c 100644
> --- a/kernel/rseq.c
> +++ b/kernel/rseq.c
> @@ -201,7 +201,7 @@ static int rseq_reset_rseq_cpu_node_id(struct task_struct *t)
> /*
> * Validate read-only rseq fields.
> */
> - if (!rseq_validate_ro_fields(t))
> + if (rseq_validate_ro_fields(t))
> return -EFAULT;
> /*
> * Reset cpu_id_start to its initial state (0).
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
next prev parent reply other threads:[~2025-01-20 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 20:59 Mathieu Desnoyers
2025-01-20 16:49 ` Mathieu Desnoyers [this message]
2025-01-21 7:24 ` [tip: sched/core] rseq: Fix rseq unregistration regression tip-bot2 for 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=525f88ba-b082-4744-b54a-a23a264fb8a3@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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®