All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michal Koutný" <mkoutny@suse.com>
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: Sebastian Chlad <sebastian.chlad@suse.com>,
	 Sebastian Chlad <sebastianchlad@gmail.com>,
	netdev@vger.kernel.org
Subject: Re: [PATCH net] selftests: af_unix: skip scm_inq tests when SO_INQ is unsupported
Date: Mon, 31 Aug 2026 17:57:34 +0200	[thread overview]
Message-ID: <apWQ7IRq5nQQTMnp@localhost.localdomain> (raw)
In-Reply-To: <CAAVpQUC3L9aUdq7M2bReCEZ5MPLPSHgC+VjzFboWdTbG=CMV=w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]

Hi Kuniyuki.

On Fri, Jul 31, 2026 at 07:53:59AM +0200, Kuniyuki Iwashima <kuniyu@google.com> wrote:
> Why is this selftest backported to the kernel without the
> functional changes ?  That's the problem.

Let me join the topic and vouch for the changes from Sebastian.

I consider there's a scale of selftests from validation of bugfixes to
checking of features. Another axis is the discoverability of the
supported features by the kernel (none ... CONFIG_ check ... runtime
indicator).

I've found it quite useful to have one set of tests that can be run
across different kernel versions (think of stable kernels), the
maintenance is simpler, sometimes even same builds may be reused.

Occasionally a reported failure raises unnecessary alarms when it is
actually only a missing or disabled feature.

So when the behavior is on the right side of the above spaces
(feature*discoverability), it is relatively easy to add a guard in the
selftest proper. That is something what've been striving for in cgroup
selftests.

Obviously, the dividing line for a good guard is not always clear cut,
in such cases it remains up to the interpreter of the test output to
decide how serious the failures are.

Here I think the ENOPROTOOPT are suitable for the feature detection.

Regards,
Michal


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 265 bytes --]

      parent reply	other threads:[~2026-08-31 15:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30 14:46 [PATCH net] selftests: af_unix: skip scm_inq tests when SO_INQ is unsupported Sebastian Chlad
2026-07-30 18:27 ` Kuniyuki Iwashima
2026-07-31  5:41   ` Sebastian Chlad
2026-07-31  5:53     ` Kuniyuki Iwashima
2026-07-31  5:57       ` Sebastian Chlad
2026-08-31 15:57       ` Michal Koutný [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=apWQ7IRq5nQQTMnp@localhost.localdomain \
    --to=mkoutny@suse.com \
    --cc=kuniyu@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=sebastian.chlad@suse.com \
    --cc=sebastianchlad@gmail.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.