From: "Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
stable-rt <stable-rt@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Daniel Wagner <daniel.wagner@suse.com>,
Tom Zanussi <tom.zanussi@linux.intel.com>,
Clark Williams <williams@redhat.com>,
Mark Gross <markgross@kernel.org>, Pavel Machek <pavel@denx.de>,
Jeff Brady <jeffreyjbrady@gmail.com>
Subject: Re: [ANNOUNCE] 5.10.201-rt98
Date: Wed, 22 Nov 2023 10:36:23 -0300 [thread overview]
Message-ID: <ZV4D1yBGSOE-OVUF@uudg.org> (raw)
In-Reply-To: <ZV1S4yDcPKwj5_N1@uudg.org>
On Tue, Nov 21, 2023 at 10:01:25PM -0300, Luis Claudio R. Goncalves wrote:
> Hello RT-list!
>
> I'm pleased to announce the 5.10.201-rt98 stable release.
>
> This release is just an update to the new stable 5.10.201
> version and no RT changes have been made.
>
> You can get this release via the git tree at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
>
> branch: v5.10-rt
> Head SHA1: 3a93f0a0d49dd0db4c6876ca9a7369350e64320e
Greg KH,
While testing v5.10.201-rt98 I stumbled over this warning:
[ 1000.312397] run blktests nvme/005 at 2023-11-21 21:46:30
...
[ 1000.500478] workqueue: WQ_MEM_RECLAIM nvmet_tcp_wq:nvmet_tcp_io_work [nvmet_tcp] is flushing !WQ_MEM_RECLAIM events:0x0
[ 1000.500490] WARNING: CPU: 0 PID: 6 at kernel/workqueue.c:2620 check_flush_dependency+0x11f/0x140
That seems to be fixed by:
533d2e8b4d5e4 nvmet-tcp: fix lockdep complaint on nvmet_tcp_wq flush during queue teardown
(and depending on what else is backported)
ddd2b8de9f85b nvmet: fix workqueue MEM_RECLAIM flushing dependency
Is this something that can be added to your v5.10 queue or should I carry
this fix on v5.10-rt in the meantime?
Thank you in advance!
Luis
> Or to build 5.10.201-rt98 directly, the following patches should be applied:
>
> https://www.kernel.org/pub/linux/kernel/v5.x/linux-5.10.tar.xz
>
> https://www.kernel.org/pub/linux/kernel/v5.x/patch-5.10.201.xz
>
> https://www.kernel.org/pub/linux/kernel/projects/rt/5.10/older/patch-5.10.201-rt98.patch.xz
>
> Signing key fingerprint:
>
> 9354 0649 9972 8D31 D464 D140 F394 A423 F8E6 7C26
>
> All keys used for the above files and repositories can be found on the
> following git repository:
>
> git://git.kernel.org/pub/scm/docs/kernel/pgpkeys.git
>
> Enjoy!
> Luis
>
---end quoted text---
next prev parent reply other threads:[~2023-11-22 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 1:01 [ANNOUNCE] 5.10.201-rt98 Luis Claudio R. Goncalves
2023-11-22 13:36 ` Luis Claudio R. Goncalves [this message]
2023-11-24 16:11 ` Greg Kroah-Hartman
2023-11-26 23:44 ` Luis Claudio R. Goncalves
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=ZV4D1yBGSOE-OVUF@uudg.org \
--to=lgoncalv@redhat.com \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=daniel.wagner@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=jeffreyjbrady@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=pavel@denx.de \
--cc=rostedt@goodmis.org \
--cc=stable-rt@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tom.zanussi@linux.intel.com \
--cc=williams@redhat.com \
/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