From: "Ahmed S. Darwish" <a.darwish@linutronix.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [ANNOUNCE] v5.11-rc4-rt1
Date: Fri, 22 Jan 2021 06:32:42 +0100 [thread overview]
Message-ID: <YApjeinzJWKYNbYb@lx-t490> (raw)
In-Reply-To: <20210121205008.GA7149@duo.ucw.cz>
On Thu, Jan 21, 2021 at 09:50:08PM +0100, Pavel Machek wrote:
> Hi!
>
> > I'm pleased to announce the v5.11-rc4-rt1 patch set.
> >
> > Changes since v5.10.8-rt24:
> >
> > - Updated to v5.11-rc4
> >
> > Known issues
> > - kdb/kgdb can easily deadlock.
> > - kmsg dumpers expecting not to be called in parallel can clobber
> > their temp buffer.
> > - netconsole triggers WARN.
>
> I noticed... lot of code using in_interrupt() to decide what to do is
> making it to 5.10-stable at the moment (and I guess that means
> vanilla, too).
>
> I have recollection that that is not okay thing to do. Am I right?
>
Correct. These macros should not be added to new, non-core, kernel code.
There's an on-going effort to clear them already, as in:
- https://lkml.kernel.org/r/20201019100629.419020859@linutronix.de (merged)
- https://lkml.kernel.org/r/20201126132952.2287996-1-bigeasy@linutronix.de (merged)
- https://lkml.kernel.org/r/20210118100955.1761652-1-a.darwish@linutronix.de (to be merged)
> Examples: 8abec36d1274bbd5ae8f36f3658b9abb3db56c31,
> d68b29584c25dbacd01ed44a3e45abb35353f1de.
>
That's sad.
Maybe it would be wise to let a bot scan lore regularly, and send an
automatic notification to authors whenever their patches reintroduce
these macros to non-core kernel code.
Thanks,
--
Ahmed S. Darwish
prev parent reply other threads:[~2021-01-22 5:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 13:45 [ANNOUNCE] v5.11-rc4-rt1 Sebastian Andrzej Siewior
2021-01-21 20:50 ` Pavel Machek
2021-01-22 5:32 ` Ahmed S. Darwish [this message]
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=YApjeinzJWKYNbYb@lx-t490 \
--to=a.darwish@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).