Netdev List
 help / color / mirror / Atom feed
From: Jori Koolstra <jkoolstra@xs4all.nl>
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: brauner@kernel.org, cyphar@cyphar.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, 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 v6 4/4] selftest: Add tests for useful handling of LSM denials on SCM_RIGHTS
Date: Wed, 5 Aug 2026 12:18:50 +0200 (CEST)	[thread overview]
Message-ID: <1227047202.267333.1785925130131@kpc.webmail.kpnmail.nl> (raw)
In-Reply-To: <CAAVpQUC7O1yiKQ+3FcGWbDkmcd-LeFc5tCC0vF7QgioVOXvb5Q@mail.gmail.com>


> Op 04-08-2026 19:26 CEST schreef Kuniyuki Iwashima <kuniyu@google.com>:
> 
> > +TEST_GEN_FILES := scm_rights_denial_lsm.bpf.o
> > +
> >  include ../../lib.mk
> > +include ../bpf.mk
> > +
> > +$(OUTPUT)/scm_rights_denial_lsm: $(BPFOBJ)
> > +$(OUTPUT)/scm_rights_denial_lsm: CFLAGS += -I$(SCRATCH_DIR)/include
> > +$(OUTPUT)/scm_rights_denial_lsm: LDLIBS += -lelf -lz
> > diff --git a/tools/testing/selftests/net/af_unix/config b/tools/testing/selftests/net/af_unix/config
> > index 41dbb03c747e..468f7a0bb64e 100644
> > --- a/tools/testing/selftests/net/af_unix/config
> > +++ b/tools/testing/selftests/net/af_unix/config
> > @@ -2,3 +2,10 @@ CONFIG_AF_UNIX_OOB=y
> >  CONFIG_UNIX=y
> >  CONFIG_UNIX_DIAG=m
> >  CONFIG_USER_NS=y
> > +CONFIG_BPF=y
> > +CONFIG_BPF_SYSCALL=y
> > +CONFIG_BPF_EVENTS=y
> > +CONFIG_BPF_JIT=y
> > +CONFIG_SECURITY=y
> > +CONFIG_BPF_LSM=y
> > +CONFIG_DEBUG_INFO_BTF=y
> 
> Please sort configs as CI complains.
> https://patchwork.kernel.org/project/netdevbpf/patch/20260802151212.3294591-5-jkoolstra@xs4all.nl/
> 
> 

Oh that is pretty neat!

I wasn't aware there was a canonical sorting for the config. This should fix it,

LC_ALL=C sort -c tools/testing/selftests/net/af_unix/config

correct?

If I fix these issues today, any chance we can still get this in before the merge window
starts again?

Best,
Jori.

  reply	other threads:[~2026-08-05 10:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-02 15:12 [PATCH net-next v6 0/4] net: af_unix: useful handling of LSM denials on SCM_RIGHTS Jori Koolstra
2026-08-02 15:12 ` [PATCH net-next v6 1/4] net: af_unix: enable custom setsockopt for all socket types Jori Koolstra
2026-08-04 16:49   ` Kuniyuki Iwashima
2026-08-02 15:12 ` [PATCH net-next v6 2/4] net: scm: move scm_detach_fds() from common path to scm_recv_unix() Jori Koolstra
2026-08-02 15:12 ` [PATCH net-next v6 3/4] net: af_unix: useful handling of LSM denials on SCM_RIGHTS Jori Koolstra
2026-08-04 17:16   ` Kuniyuki Iwashima
2026-08-05 10:09     ` Jori Koolstra
2026-08-05 16:27       ` Kuniyuki Iwashima
2026-08-02 15:12 ` [PATCH net-next v6 4/4] selftest: Add tests for " Jori Koolstra
2026-08-04 17:26   ` Kuniyuki Iwashima
2026-08-05 10:18     ` Jori Koolstra [this message]
2026-08-05 16:30       ` Kuniyuki Iwashima

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=1227047202.267333.1785925130131@kpc.webmail.kpnmail.nl \
    --to=jkoolstra@xs4all.nl \
    --cc=brauner@kernel.org \
    --cc=cyphar@cyphar.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox