From: Nam Cao <namcao@linutronix.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
John Ogness <john.ogness@linutronix.de>,
Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rt-devel@lists.linux.dev, linux-rt-users@vger.kernel.org,
Joe Damato <jdamato@fastly.com>,
Martin Karsten <mkarsten@uwaterloo.ca>,
Jens Axboe <axboe@kernel.dk>,
Frederic Weisbecker <frederic@kernel.org>,
Valentin Schneider <vschneid@redhat.com>
Subject: Re: [PATCH v3] eventpoll: Fix priority inversion problem
Date: Wed, 25 Jun 2025 18:02:27 +0200 [thread overview]
Message-ID: <20250625160227.B9-NAdc2@linutronix.de> (raw)
In-Reply-To: <20250625155713.lckVkmJH@linutronix.de>
On Wed, Jun 25, 2025 at 05:57:18PM +0200, Nam Cao wrote:
> On Wed, Jun 25, 2025 at 05:33:54PM +0200, Sebastian Andrzej Siewior wrote:
> > On 2025-06-25 17:27:02 [+0200], Nam Cao wrote:
> > > To be sure, I tried your suggestion. Systemd sometimes failed to boot, and
> > > my stress test crashed instantly.
> >
> > I had a trace_printk() there while testing and it never triggered.
>
> This code path is only executed for broken userspace.
Forgot to mention, my test crashed because the __llist_add(n, &txlist)
below doesn't care if 'n' is already in a list. By changing to from
llist_del_first() to llist_del_first_init(), it is possible for 'n' to be
in a list, therefore __llist_add() would break.
Nam
next prev parent reply other threads:[~2025-06-25 16:02 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 9:08 [PATCH v3] eventpoll: Fix priority inversion problem Nam Cao
2025-05-30 5:08 ` Christian Brauner
2025-06-25 15:35 ` Sebastian Andrzej Siewior
2025-06-26 13:35 ` Frederic Weisbecker
2025-06-26 13:51 ` Sebastian Andrzej Siewior
2025-06-25 14:50 ` Sebastian Andrzej Siewior
2025-06-25 15:27 ` Nam Cao
2025-06-25 15:33 ` Sebastian Andrzej Siewior
2025-06-25 15:57 ` Nam Cao
2025-06-25 16:02 ` Nam Cao [this message]
2025-06-26 15:23 ` John Ogness
2025-06-26 15:49 ` Sebastian Andrzej Siewior
2025-06-26 15:56 ` Nam Cao
2025-06-30 15:08 ` K Prateek Nayak
2025-07-01 20:33 ` Florian Bezdeka
2025-07-01 12:03 ` Christian Brauner
2025-07-10 3:08 ` Xi Ruoyao
2025-07-10 3:48 ` Nam Cao
2025-07-10 4:06 ` Nam Cao
2025-07-10 4:10 ` Xi Ruoyao
2025-07-10 6:21 ` Nam Cao
2025-07-10 6:54 ` Xi Ruoyao
2025-07-10 8:32 ` Nam Cao
2025-07-10 9:47 ` Xi Ruoyao
2025-07-11 5:02 ` Nam Cao
2025-07-11 9:44 ` Christian Brauner
2025-07-11 9:48 ` Xi Ruoyao
2025-07-11 9:58 ` Nam Cao
2025-07-11 12:09 ` Xi Ruoyao
2025-07-11 12:21 ` Nam Cao
2025-07-12 0:09 ` Nam Cao
2025-07-12 8:54 ` Xi Ruoyao
2025-07-11 9:50 ` Nam Cao
2025-07-14 8:59 ` Christian Brauner
2025-07-14 10:14 ` Nam Cao
2025-07-15 9:37 ` Yann Ylavic
2025-07-15 10:08 ` Nam Cao
2025-07-14 16:16 ` Linus Torvalds
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=20250625160227.B9-NAdc2@linutronix.de \
--to=namcao@linutronix.de \
--cc=axboe@kernel.dk \
--cc=bigeasy@linutronix.de \
--cc=brauner@kernel.org \
--cc=clrkwllms@kernel.org \
--cc=frederic@kernel.org \
--cc=jack@suse.cz \
--cc=jdamato@fastly.com \
--cc=john.ogness@linutronix.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=linux-rt-users@vger.kernel.org \
--cc=mkarsten@uwaterloo.ca \
--cc=rostedt@goodmis.org \
--cc=viro@zeniv.linux.org.uk \
--cc=vschneid@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 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.