netdev - Re: [PATCH net-next v5 00/12] Begin upstreaming Homa transport protocol

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: <CAGXJAmxKsVwJ3Ty0jhQ3s5geOMD1WWBhBQK-9DcnH519xUV3Hg@mail.gmail.com>
Date: Mon, 13 Jan 2025 12:47:48 -0800
From: John Ousterhout <ouster@...stanford.edu>
To: Andrew Lunn <andrew@...n.ch>
Cc: netdev@...r.kernel.org, pabeni@...hat.com, edumazet@...gle.com, 
	horms@...nel.org, kuba@...nel.org
Subject: Re: [PATCH net-next v5 00/12] Begin upstreaming Homa transport protocol

On Mon, Jan 13, 2025 at 12:06 PM Andrew Lunn <andrew@...n.ch> wrote:
>
> On Mon, Jan 13, 2025 at 09:27:34AM -0800, John Ousterhout wrote:
> > The Patchwork Web page for this patch set
> > (https://patchwork.kernel.org/project/netdevbpf/list/?series=922654&state=*)
> > is showing errors for the "netdev/contest" context for each of the
> > patches in the series. The errors are the same for each patch, and
> > they seem to be coming from places other than Homa.
>
> Hi John
>
> The tests take too long to run for each patchset, so i _think_ all
> patches in a 3 hour window are tested in a batch. So it could well be
> some other patchset in the batch broke something.
>
> You should be able to run the test yourself, on your own build.
> https://netdev-3.bots.linux.dev/vmksft-net-dbg/results/937341/60-bpf-offload-py/stdout
> shows you the command line. However, the test environment, what tools
> you need installed etc, is less clear.
>
> To me, it does seem unlikely that HOMA would cause:
>
> cat: /sys/kernel/debug/netdevsim/netdevsim20347//ports/0//queue_reset:
> Invalid argument
>
> So i would not worry about it too much. However, if the next
> submission has the same issues....

Thanks for the information; I'll take your advice and see if the
problem goes away with the next submission.

-John-