netdev - Re: [PATCH net-next v2 10/12] selftests: ncdevmem: Run selftest when none of the -s or -c has been provided

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHS8izM1MGAurmE76nO9vBkura-+kAwJET_Az6UhPsw49a1J7Q@mail.gmail.com>
Date: Thu, 3 Oct 2024 12:10:02 -0700
From: Mina Almasry <almasrymina@...gle.com>
To: Stanislav Fomichev <stfomichev@...il.com>
Cc: Stanislav Fomichev <sdf@...ichev.me>, netdev@...r.kernel.org, davem@...emloft.net, 
	edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com
Subject: Re: [PATCH net-next v2 10/12] selftests: ncdevmem: Run selftest when
 none of the -s or -c has been provided

On Thu, Oct 3, 2024 at 10:18 AM Stanislav Fomichev <stfomichev@...il.com> wrote:
>
> On 10/03, Mina Almasry wrote:
> > On Mon, Sep 30, 2024 at 10:18 AM Stanislav Fomichev <sdf@...ichev.me> wrote:
> > >
> > > This will be used as a 'probe' mode in the selftest to check whether
> > > the device supports the devmem or not.
> >
> > It's not really 'probing'. Running ncdevmem with -s or -c does the
> > data path tests. Running ncdevmem without does all the control path
> > tests in run_devmem_tests(). It's not just probing driver for support,
> > it's mean to catch bugs. Maybe rename to 'control path tests' or
> > 'config tests' instead of probing.
>
> Re 'probing' vs 'control path tests': I need something I can call
> in the python selftest to tell me whether the nic supports devmem
> or not (to skip the tests on the unsupported nics), so I'm reusing this
> 'control path tests' mode for this. I do agree that there might be an
> issue where the nic supports devmem, but has some bug which causes
> 'control path tests' to fail which leads to skipping the data plane tests...
>
> We can try to separate these two in the future. (and I'll keep the word
> 'probing' for now since it's only in the commit message to describe the
> intent)

Ah, got it. Thanks for the explanation.

Complete probing should call the binding API and assert that the
return is EOPNOTSUPP or something like that. Other errors in the
control path tests should be considered failures and not test skips.
But probing is necessary to run this test and this is a good way to do
it for now. We can improve later if necessary. Thanks!

-- 
Thanks,
Mina