From: Thomas Gleixner <tglx@linutronix.de>
To: Mateusz Guzik <mjguzik@gmail.com>,
Bert Karwatzki <spasswolf@web.de>,
Christian Brauner <brauner@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
linux-rt-devel@lists.linux.dev, linux-fsdevel@vger.kernel.org,
adobriyan@gmail.com, jack@suse.cz, viro@zeniv.linux.org.uk,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: context switch within RCU read-side critical section in next-20260518+ with PREEMPT_RT
Date: Thu, 21 May 2026 12:05:27 +0200 [thread overview]
Message-ID: <87bje9w00o.ffs@tglx> (raw)
In-Reply-To: <fnrz73n5jojl2wlbgrsjdtu5zuwykwbcjzznaijbquuovpoand@i6ihdqn7a6zv>
On Thu, May 21 2026 at 10:53, Mateusz Guzik wrote:
> On Thu, May 21, 2026 at 12:52:44AM +0200, Bert Karwatzki wrote:
>> With these reverts next-20260519 boots 30 times in a row without error, so
>> it appears that commit dc651e25a6d2 ("fs: RCU-ify filesystems list") causing the
>> error.
>>
>
> I think the patch below will do the trick.
>
> If someone wonders how come the missing unlocks: the original patch had
> them in place, but when I was rebasing on top of the RCU-ifing commit I
> figured I'm going to do guard/scoped_guard in there as well. Later it
> started failing as the compiler did not like goto retry out of a scoped
> guard area and the unlocks did not come back.
>
> tl;dr there is definitely my bug here and it is most likely *the* bug
I was staring at the wrong commit then :)
next prev parent reply other threads:[~2026-05-21 10:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 22:52 context switch within RCU read-side critical section in next-20260518+ with PREEMPT_RT Bert Karwatzki
2026-05-21 8:37 ` Thomas Gleixner
2026-05-21 8:53 ` Mateusz Guzik
2026-05-21 9:08 ` Sebastian Andrzej Siewior
2026-05-21 9:17 ` Mateusz Guzik
2026-05-21 9:09 ` Mateusz Guzik
2026-05-21 9:20 ` Bert Karwatzki
2026-05-21 9:25 ` Mateusz Guzik
2026-05-21 9:57 ` Bert Karwatzki
2026-05-21 10:17 ` Thomas Gleixner
2026-05-21 10:21 ` Bert Karwatzki
2026-05-21 10:33 ` Mateusz Guzik
2026-05-21 11:50 ` Bert Karwatzki
2026-05-21 12:01 ` Mateusz Guzik
2026-05-28 17:59 ` Bert Karwatzki
2026-05-29 17:20 ` Mateusz Guzik
2026-05-21 12:55 ` [PATCH] amd/amdkfd: Initialize kfd_dev::profiler lock early Thomas Gleixner
2026-05-21 10:05 ` Thomas Gleixner [this message]
2026-05-21 10:13 ` context switch within RCU read-side critical section in next-20260518+ with PREEMPT_RT Bert Karwatzki
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=87bje9w00o.ffs@tglx \
--to=tglx@linutronix.de \
--cc=adobriyan@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=mjguzik@gmail.com \
--cc=spasswolf@web.de \
--cc=viro@zeniv.linux.org.uk \
/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.