Netdev List
 help / color / mirror / Atom feed
From: Nam Cao <namcao@linutronix.de>
To: Kuniyuki Iwashima <kuniyu@google.com>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH net-next v4 0/1] af_unix: Fix priority inversion issue
Date: Tue, 01 Sep 2026 09:17:44 +0200	[thread overview]
Message-ID: <871pbdbftz.fsf@yellow.woof> (raw)
In-Reply-To: <cover.1785824313.git.namcao@linutronix.de>

Hi,

Nam Cao <namcao@linutronix.de> writes:
> While auditing AF_UNIX sockets, I noticed that the sendmsg() code paths may
> block on the garbage collector running as workqueue. This can cause
> priority inversion and latency for real-time users.
>
> The implementation does kindly avoid blocking "sane users". However, it is
> impossible to tell whether the kernel's definition of "sane users"
> accurately describes all users out there.
>
> Digging into history and figuring out the reasons why sendmsg() needs to
> wait for garbage collector, it is determined that those reasons no longer
> apply.

I just looked at patchwork and noticed that this patch is marked as
"Changes Requested", but I'm not sure what changes are still expected.

Did I miss a question or an issue that still needs to be addressed?

Nam

      parent reply	other threads:[~2026-09-01  7:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04  6:46 [PATCH net-next v4 0/1] af_unix: Fix priority inversion issue Nam Cao
2026-08-04  6:46 ` [PATCH net-next v4 1/1] af_unix: Do not wait for garbage collector in sendmsg() Nam Cao
2026-08-08  1:07   ` Jakub Kicinski
2026-08-08  1:40     ` Kuniyuki Iwashima
2026-08-08  4:07       ` Nam Cao
2026-09-01  7:17 ` Nam Cao [this message]

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=871pbdbftz.fsf@yellow.woof \
    --to=namcao@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@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