All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yuqi Xu <xuyuqiabc@gmail.com>
Cc: netdev@vger.kernel.org, tung.quang.nguyen@est.tech,
	jmaloy@redhat.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
	ying.xue@windriver.com, paul.gortmaker@windriver.com,
	tipc-discussion@lists.sourceforge.net, stable@vger.kernel.org,
	vega@nebusec.ai, weir@nebusec.ai, xuyq21@lenovo.com
Subject: Re: [PATCH net v3 0/1] tipc: fix connection lifetime during netns teardown
Date: Fri, 02 Oct 2026 07:30:04 +0000	[thread overview]
Message-ID: <179092620470.3255919.5798329949179493943.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1790157006.git.xuyuqiabc@gmail.com>

Hello:

This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:

On Mon, 28 Sep 2026 16:24:37 +0800 you wrote:
> Hi Linux kernel maintainers,
> 
> We found and validated an issue in net/tipc/topsrv.c. The PoC
> supports --userns (CLONE_NEWUSER|CLONE_NEWNET) for an unprivileged
> user, but the captured traces are root mode.
> 
> We've tested it, and it should not affect any other functionality.
> 
> [...]

Here is the summary with links:
  - [net,v3,1/1] tipc: destroy topsrv workqueues before closing connections
    https://git.kernel.org/netdev/net/c/3acdd44385bc

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-02  7:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28  8:24 [PATCH net v3 0/1] tipc: fix connection lifetime during netns teardown Yuqi Xu
2026-09-28  8:24 ` [PATCH net v3 1/1] tipc: destroy topsrv workqueues before closing connections Yuqi Xu
2026-10-02  7:30 ` patchwork-bot+netdevbpf [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=179092620470.3255919.5798329949179493943.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jmaloy@redhat.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=stable@vger.kernel.org \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=tung.quang.nguyen@est.tech \
    --cc=vega@nebusec.ai \
    --cc=weir@nebusec.ai \
    --cc=xuyq21@lenovo.com \
    --cc=xuyuqiabc@gmail.com \
    --cc=ying.xue@windriver.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.