From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Oleg Nesterov <oleg@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@kernel.org>,
Ben Segall <bsegall@google.com>, Borislav Petkov <bp@alien8.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>, Mel Gorman <mgorman@suse.de>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [PATCH] signal/x86: Delay calling signals in atomic
Date: Mon, 28 Mar 2022 18:32:46 +0200 [thread overview]
Message-ID: <YkHjLkDsA4oYj9rU@linutronix.de> (raw)
In-Reply-To: <87h77iw34u.fsf@email.froward.int.ebiederm.org>
On 2022-03-28 09:41:37 [-0500], Eric W. Biederman wrote:
> I want to say the patch below looks like it was a perfectly fine debug
> patch to see if what someone thinks is the issue is the issue. It is
> not a good final solution for the reasons I have already mentioned.
>
> May I ask where the rest of the conversation was? I can only find the
> single posting of this patch on linux-kernel without any conversation,
> and the description indicates this change has seen several rounds of
> development.
There was not feedback based on what has been posted to lkml.
This, was ended as this patch, was originally posted by Steven as
https://lore.kernel.org/linux-rt-users/20120124191454.345715521@goodmis.org/
a few iterations later we got to v4 in
https://lore.kernel.org/linux-rt-users/20120203183041.427463295@goodmis.org/
which got review from Oleg and then become Oleg's in v5
https://lore.kernel.org/linux-rt-users/20120208005850.233662427@goodmis.org/
and was part of the RT queue since v3.0.20-rt36.
> Eric
Sebastian
next prev parent reply other threads:[~2022-03-28 16:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 20:19 [PATCH] signal/x86: Delay calling signals in atomic Sebastian Andrzej Siewior
2022-03-28 14:25 ` Eric W. Biederman
2022-03-28 14:41 ` Eric W. Biederman
2022-03-28 16:32 ` Sebastian Andrzej Siewior [this message]
2022-03-28 14:48 ` Eric W. Biederman
2022-03-28 16:17 ` Sebastian Andrzej Siewior
2022-03-28 22:07 ` Eric W. Biederman
2022-03-29 9:31 ` Sebastian Andrzej Siewior
2022-03-30 18:10 ` Eric W. Biederman
2022-04-01 11:45 ` Sebastian Andrzej Siewior
2022-04-04 14:29 ` Eric W. Biederman
2022-03-28 16:28 ` Thomas Gleixner
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=YkHjLkDsA4oYj9rU@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dave.hansen@linux.intel.com \
--cc=dietmar.eggemann@arm.com \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.