netdev - Re: [PATCH net v2 3/3] selftests: net: test for lwtunnel dst ref loops

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: <e5d0e758-f68f-4bf7-9fdc-b8171210e3a1@uliege.be>
Date: Thu, 20 Mar 2025 16:38:35 +0100
From: Justin Iurman <justin.iurman@...ege.be>
To: Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org
Cc: davem@...emloft.net, dsahern@...nel.org, edumazet@...gle.com,
 kuba@...nel.org, horms@...nel.org, Shuah Khan <shuah@...nel.org>,
 linux-kselftest@...r.kernel.org
Subject: Re: [PATCH net v2 3/3] selftests: net: test for lwtunnel dst ref
 loops

On 3/20/25 11:25, Paolo Abeni wrote:
> On 3/14/25 1:00 PM, Justin Iurman wrote:
>> As recently specified by commit 0ea09cbf8350 ("docs: netdev: add a note
>> on selftest posting") in net-next, the selftest is therefore shipped in
>> this series. However, this selftest does not really test this series. It
>> needs this series to avoid crashing the kernel. What it really tests,
>> thanks to kmemleak,
> 
> As a net-next follow-up you could force a kmemleak scan and check the
> result after each test case to really output a pass/fail message.

Sure. Could you point me to an example doing that? Not sure how I'd 
force it within the selftest.

> Also, still for net-next, please investigate if dropping or reducing the
> many sleep below could be possible (it's not clear to me why they are
> needed).

Of course, will do.

> I'll take is as-is to avoid blocking the fixes for trivial matters.

Thanks,
Justin

> Thanks,
> 
> Paolo
>