mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: tjdqudcks0424@naver.com
Cc: bsingharora@gmail.com, akpm@linux-foundation.org,
	xu.xin@linux.dev, shuah@kernel.org, cyyzero16@gmail.com,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v3 0/2] taskstats: fix cross-netns exit listener delivery
Date: Fri, 2 Oct 2026 13:06:29 +0200	[thread overview]
Message-ID: <2026100208-gray-yiddish-d249@gregkh> (raw)
In-Reply-To: <20261002105614.195370-1-tjdqudcks0424@naver.com>

On Fri, Oct 02, 2026 at 07:56:12PM +0900, tjdqudcks0424@naver.com wrote:
> From: 성병찬 <tjdqudcks0424@naver.com>
> 
> CPU-mask taskstats listeners are currently identified only by a numeric
> Generic Netlink port ID and exit records are sent through init_net. Since
> port IDs are namespace-local, an unprivileged init_net socket can bind the
> same number as a listener in another network namespace and receive that
> listener's cross-UID exit record.
> 
> Patch 1 associates listener entries with the registering Generic Netlink
> socket's namespace and port ID and cleans them up when that socket closes.
> Patch 2 adds an acct kselftest which constructs the collision and checks the
> normal listener, explicit deregistration, and unrelated-port controls.
> 
> The test was built with GCC using -Wall -Wextra and run in disposable QEMU
> guests with the same userspace binary. On the unmodified baseline it reports
> 3 passes and 1 failure: the child-netns listener misses the victim record and
> the colliding unprivileged init_net socket receives it. On the fixed kernel,
> three independent clean boots each report 4 passes and no failures. No
> KASAN, UBSAN, BUG, WARNING, Oops, panic, lockdep, refcount, use-after-free,
> out-of-bounds, or kmemleak diagnostic was emitted during the final runs.
> 
> The exact Message-ID and lore URL of the previous public posting were not
> present in the available local sent-mail or raw-mail artifacts:
> 
> Link: https://lore.kernel.org/r/20261002075842.146026-1-tjdqudcks0424@naver.com/

Please slow down, there's no rush here and you aren't giving people a
chance to test or review any of this.

thanks,

greg k-h

      parent reply	other threads:[~2026-10-02 11:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 10:56 tjdqudcks0424
2026-10-02 10:56 ` [PATCH v3 1/2] taskstats: route exit listener records through their netns tjdqudcks0424
2026-10-02 16:40   ` Bradley Morgan
2026-10-02 10:56 ` [PATCH v3 2/2] selftests: acct: test taskstats listener netns routing tjdqudcks0424
2026-10-02 16:43   ` Bradley Morgan
2026-10-03  2:24     ` tjdqudcks0424
2026-10-02 11:06 ` Greg KH [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=2026100208-gray-yiddish-d249@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=bsingharora@gmail.com \
    --cc=cyyzero16@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=tjdqudcks0424@naver.com \
    --cc=xu.xin@linux.dev \
    /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

all inboxes | Powered by JetHome®