[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YkHjLkDsA4oYj9rU@linutronix.de>
Date: Mon, 28 Mar 2022 18:32:46 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: x86@...nel.org, linux-kernel@...r.kernel.org,
Oleg Nesterov <oleg@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Andy Lutomirski <luto@...nel.org>,
Ben Segall <bsegall@...gle.com>,
Borislav Petkov <bp@...en8.de>,
Daniel Bristot de Oliveira <bristot@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Ingo Molnar <mingo@...hat.com>,
Juri Lelli <juri.lelli@...hat.com>,
Mel Gorman <mgorman@...e.de>,
Peter Zijlstra <peterz@...radead.org>,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>,
Vincent Guittot <vincent.guittot@...aro.org>
Subject: Re: [PATCH] signal/x86: Delay calling signals in atomic
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
Powered by blists - more mailing lists