Subject: [ANNOUNCE] v5.11-rc4-rt1

Dear RT folks!

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.

You can get this release via the git tree at:

git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git v5.11-rc4-rt1

The RT patch against v5.11-rc4 can be found here:

https://cdn.kernel.org/pub/linux/kernel/projects/rt/5.11/older/patch-5.11-rc4-rt1.patch.xz

The split quilt queue is available at:

https://cdn.kernel.org/pub/linux/kernel/projects/rt/5.11/older/patches-5.11-rc4-rt1.tar.xz

Sebastian


2021-01-21 20:54:30

by Pavel Machek

[permalink] [raw]
Subject: Re: [ANNOUNCE] v5.11-rc4-rt1

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?

Examples: 8abec36d1274bbd5ae8f36f3658b9abb3db56c31,
d68b29584c25dbacd01ed44a3e45abb35353f1de.

Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek

Attachments:
(No filename) (729.00 B)
 signature.asc (201.00 B)
 Download all attachments

2021-01-22 05:53:31

by Ahmed S. Darwish

[permalink] [raw]
Subject: Re: [ANNOUNCE] v5.11-rc4-rt1

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/[email protected] (merged)
- https://lkml.kernel.org/r/[email protected] (merged)
- https://lkml.kernel.org/r/[email protected] (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