Netdev List
 help / color / mirror / Atom feed
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Anna Nyiri <annaemesenyiri@gmail.com>,  Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org,  fejes@inf.elte.hu,  edumazet@google.com,
	 kuba@kernel.org,  willemb@google.com,  idosch@idosch.org,
	 horms@kernel.org,  davem@davemloft.net,  shuah@kernel.org,
	 linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v2] selftests: net: Add support for testing SO_RCVMARK and SO_RCVPRIORITY
Date: Thu, 13 Feb 2025 10:06:38 -0500	[thread overview]
Message-ID: <67ae0a7e9b5f6_24be4529453@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <CAKm6_Rv4LCpy6KaV84gOi7wW7OKdasbx2zqfFwFG26=L6rkhgA@mail.gmail.com>

Anna Nyiri wrote:
> Paolo Abeni <pabeni@redhat.com> ezt írta (időpont: 2025. febr. 11., K, 12:19):
> >
> > On 2/10/25 8:22 PM, Anna Emese Nyiri wrote:
> > > Introduce tests to verify the correct functionality of the SO_RCVMARK and
> > > SO_RCVPRIORITY socket options.
> > >
> > > Key changes include:
> > >
> > > - so_rcv_listener.c: Implements a receiver application to test the correct
> > > behavior of the SO_RCVMARK and SO_RCVPRIORITY options.
> > > - test_so_rcv.sh: Provides a shell script to automate testing for these options.
> > > - Makefile: Integrates test_so_rcv.sh into the kernel selftests.
> > >
> > > v2:
> > >
> > > - Add the C part to TEST_GEN_PROGS and .gitignore.
> > > - Modify buffer space and add IPv6 testing option
> > > in so_rcv_listener.c.
> > > - Add IPv6 testing, remove unnecessary comment,
> > > add kselftest exit codes, run both binaries in a namespace,
> > > and add sleep in test_so_rcv.sh.
> > > The sleep was added to ensure that the listener process has
> > > enough time to start before the sender attempts to connect.
> > > - Rebased on net-next.
> > >
> > > v1:
> > >
> > > https://lore.kernel.org/netdev/20250129143601.16035-2-annaemesenyiri@gmail.com/
> >
> > Unfortunately the added self-test does not run successfully in the CI:
> 
> I think the test is not running because it is added to TEST_GEN_PROGS.
> However, after reconsidering, I'm not sure it should be there, since
> this test does not run on its own but is executed by the
> test_so_rcv.sh shell script.
> Wouldn't it be more appropriate to add so_rcv_listener to
> TEST_GEN_FILES instead?

Yes,

+TEST_PROGS += test_so_rcv.sh

is correct, as this needs to be called from kselftest.

+TEST_GEN_PROGS += so_rcv_listener

needs to be TEST_GEN_FILES as it is not intended to be called directly.

Documentation/dev-tools/kselftest.rst for details.

  reply	other threads:[~2025-02-13 15:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 19:22 [PATCH net-next v2] selftests: net: Add support for testing SO_RCVMARK and SO_RCVPRIORITY Anna Emese Nyiri
2025-02-11 11:19 ` Paolo Abeni
2025-02-13 12:46   ` Anna Nyiri
2025-02-13 15:06     ` Willem de Bruijn [this message]
2025-02-12  1:41 ` Willem de Bruijn

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=67ae0a7e9b5f6_24be4529453@willemb.c.googlers.com.notmuch \
    --to=willemdebruijn.kernel@gmail.com \
    --cc=annaemesenyiri@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fejes@inf.elte.hu \
    --cc=horms@kernel.org \
    --cc=idosch@idosch.org \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    --cc=willemb@google.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