Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yafang Shao <laoar.shao@gmail.com>
Cc: stephen@networkplumber.org, kuniyu@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH v2 iproute2-next] ss: stop displaying dccp sockets
Date: Thu, 09 Jul 2026 14:40:06 +0000	[thread overview]
Message-ID: <178360800689.3521873.4056238946296200606.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260701025005.76589-1-laoar.shao@gmail.com>

Hello:

This patch was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:

On Wed,  1 Jul 2026 10:50:05 +0800 you wrote:
> DCCP support was retired in kernel commit 2a63dd0edf38 ("net: Retire
> DCCP socket."). However, ss still attempts to query DCCP sockets via
> netlink, which triggers repeated SELinux warnings in dmesg:
> 
>   SELinux: unrecognized netlink message: protocol=4 nlmsg_type=19 \
>     sclass=netlink_tcpdiag_socket pid=188945 comm=ss
> 
> [...]

Here is the summary with links:
  - [v2,iproute2-next] ss: stop displaying dccp sockets
    https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=3c0b939e88e4

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



  reply	other threads:[~2026-07-09 14:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30 11:41 [PATCH iproute2-next] ss: stop displaying dccp sockets Yafang Shao
2026-06-30 23:13 ` Kuniyuki Iwashima
2026-07-01  1:56   ` Stephen Hemminger
2026-07-01  2:50     ` [PATCH v2 " Yafang Shao
2026-07-09 14:40       ` patchwork-bot+netdevbpf [this message]
2026-07-01  1:55 ` [PATCH " Stephen Hemminger

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=178360800689.3521873.4056238946296200606.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=kuniyu@google.com \
    --cc=laoar.shao@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    /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