From: Jakub Kicinski <kuba@kernel.org>
To: Jori Koolstra <jkoolstra@xs4all.nl>
Cc: brauner@kernel.org, cyphar@cyphar.com, kuniyu@google.com,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
horms@kernel.org, netdev@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v7 0/4] net: af_unix: useful handling of LSM denials on SCM_RIGHTS
Date: Fri, 14 Aug 2026 10:18:28 -0700 [thread overview]
Message-ID: <20260814101828.2ea54f8a@kernel.org> (raw)
In-Reply-To: <1036785927.390839.1786639504241@kpc.webmail.kpnmail.nl>
On Thu, 13 Aug 2026 18:45:04 +0200 (CEST) Jori Koolstra wrote:
> My "smart" email provider blocker me from sending more email. Since I am in South Korea
> that is apparently suspicious. Now patch 4 is missing. I'll try to rectify that. Is there
> any sane email provider that any of you use?
Ah.. shit. I crashed out at you on patch 4 assuming the rest of
the code is in LSM.
You gotta repost the whole thing, sorry. Patchwork (and lore) weren't
able to connect the dots. We have 2 separate incomplete series in PW.
next prev parent reply other threads:[~2026-08-14 17:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 16:28 [PATCH net-next v7 0/4] net: af_unix: useful handling of LSM denials on SCM_RIGHTS Jori Koolstra
2026-08-13 16:28 ` [PATCH net-next v7 1/4] net: af_unix: enable custom setsockopt for all socket types Jori Koolstra
2026-08-13 16:28 ` [PATCH net-next v7 2/4] net: scm: move scm_detach_fds() from common path to scm_recv_unix() Jori Koolstra
2026-08-13 16:28 ` [PATCH net-next v7 3/4] net: af_unix: useful handling of LSM denials on SCM_RIGHTS Jori Koolstra
2026-08-13 16:45 ` [PATCH net-next v7 0/4] " Jori Koolstra
2026-08-14 17:18 ` Jakub Kicinski [this message]
2026-08-14 17:32 ` Jori Koolstra
2026-08-14 18:45 ` Jakub Kicinski
2026-08-14 17:28 ` [PATCH net-next v7 4/4] selftest: Add tests for " Jori Koolstra
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=20260814101828.2ea54f8a@kernel.org \
--to=kuba@kernel.org \
--cc=brauner@kernel.org \
--cc=cyphar@cyphar.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jkoolstra@xs4all.nl \
--cc=kuniyu@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.