From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: John Ogness <john.ogness@linutronix.de>
Cc: Nam Cao <namcao@linutronix.de>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
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: Thu, 26 Jun 2025 17:49:54 +0200 [thread overview]
Message-ID: <20250626154954.NH9L0mtz@linutronix.de> (raw)
In-Reply-To: <841pr6msql.fsf@jogness.linutronix.de>
On 2025-06-26 17:29:46 [+0206], John Ogness wrote:
> > @@ -361,10 +348,14 @@ static inline int ep_cmp_ffd(struct epoll_filefd *p1,
> > (p1->file < p2->file ? -1 : p1->fd - p2->fd));
> > }
> >
> > -/* Tells us if the item is currently linked */
> > -static inline int ep_is_linked(struct epitem *epi)
> > +/*
> > + * Add the item to its container eventpoll's rdllist; do nothing if the item is already on rdllist.
> > + */
> > +static void epitem_ready(struct epitem *epi)
> > {
> > - return !list_empty(&epi->rdllink);
> > + if (&epi->rdllink == cmpxchg(&epi->rdllink.next, &epi->rdllink, NULL))
>
> Perhaps:
>
> if (try_cmpxchg(&epi->rdllink.next, &epi->rdllink, NULL))
Not sure this is the same.
This will write back the current value of epi->rdllink.next to
epi->rdllink if epi->rdllink.next is not &epi->rdllink.
The intention is to check if epi->rdllink.next is set to &epi->rdllink
(pointing to itself) and if so set it NULL just to avoid to ensure
further cmpxchg() will fail here.
> > + llist_add(&epi->rdllink, &epi->ep->rdllist);
> > +
> > }
> >
> > static inline struct eppoll_entry *ep_pwq_from_wait(wait_queue_entry_t *p)
>
> John Ogness
Sebastian
next prev parent reply other threads:[~2025-06-26 15:49 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
2025-06-26 15:23 ` John Ogness
2025-06-26 15:49 ` Sebastian Andrzej Siewior [this message]
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=20250626154954.NH9L0mtz@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=axboe@kernel.dk \
--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=namcao@linutronix.de \
--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 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).