From: Oleg Nesterov <oleg@redhat.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH REPOST 2/2] signal: Don't disable preemption in ptrace_stop() on PREEMPT_RT.
Date: Tue, 6 Jun 2023 13:04:48 +0200 [thread overview]
Message-ID: <20230606110447.GA7542@redhat.com> (raw)
In-Reply-To: <20230606085524.2049961-3-bigeasy@linutronix.de>
The patch LGTM, but I am a bit confused by the changelog/comments,
I guess I missed something...
On 06/06, Sebastian Andrzej Siewior wrote:
>
> --- a/kernel/signal.c
> +++ b/kernel/signal.c
> @@ -2328,11 +2328,16 @@ static int ptrace_stop(int exit_code, int why, unsigned long message,
> * The preempt-disable section ensures that there will be no preemption
> * between unlock and schedule() and so improving the performance since
> * the ptracer has no reason to sleep.
> + *
> + * This optimisation is not doable on PREEMPT_RT due to the spinlock_t
> + * within the preempt-disable section.
> */
> - preempt_disable();
> + if (!IS_ENABLED(CONFIG_PREEMPT_RT))
> + preempt_disable();
Not only we the problems with cgroup_enter_frozen(), afaics (please correct me)
this optimisation doesn't work on RT anyway?
IIUC, read_lock() on RT disables migration but not preemption, so it is simply
too late to do preempt_disable() before unlock/schedule. The tracer can preempt
the tracee right after do_notify_parent_cldstop().
Oleg.
next prev parent reply other threads:[~2023-06-06 11:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 8:55 [PATCH REPOST 0/2] signal: Avoid preempt_disable() in ptrace_stop() on PREEMPT_RT Sebastian Andrzej Siewior
2023-06-06 8:55 ` [PATCH REPOST 1/2] signal: Add proper comment about the preempt-disable in ptrace_stop() Sebastian Andrzej Siewior
2023-06-06 11:06 ` Oleg Nesterov
2023-06-06 8:55 ` [PATCH REPOST 2/2] signal: Don't disable preemption in ptrace_stop() on PREEMPT_RT Sebastian Andrzej Siewior
2023-06-06 11:04 ` Oleg Nesterov [this message]
2023-06-06 11:14 ` Peter Zijlstra
2023-06-06 11:38 ` Oleg Nesterov
2023-06-06 13:16 ` [PATCH 2/2 v2] " Sebastian Andrzej Siewior
2023-06-06 13:20 ` Oleg Nesterov
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=20230606110447.GA7542@redhat.com \
--to=oleg@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--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