netdev - Re: XDP Performance Regression in recent kernel versions

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: <87ed8mftra.fsf@toke.dk>
Date: Mon, 24 Jun 2024 13:46:33 +0200
From: Toke Høiland-Jørgensen <toke@...hat.com>
To: Samuel Dobron <sdobron@...hat.com>, Daniel Borkmann
 <daniel@...earbox.net>, hawk@...nel.org
Cc: Sebastiano Miano <mianosebastiano@...il.com>, bpf@...r.kernel.org,
 netdev@...r.kernel.org, saeedm@...dia.com, tariqt@...dia.com,
 edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com
Subject: Re: XDP Performance Regression in recent kernel versions

Samuel Dobron <sdobron@...hat.com> writes:

>> It looks like this is known since March, was this ever reported to Nvidia back
>> then? :/
>
> Not sure if that's a question for me, I was told, filling an issue in
> Bugzilla/Jira is where
> our competences end. Who is supposed to report it to them?

I don't think we have a formal reporting procedure, but I was planning
to send this to the list, referencing the Bugzilla entry. Seems I
dropped the ball on that; sorry! :(

Can we set up a better reporting procedure for this going forward? A
mailing list, or just a name we can put in reports? Or something else?
Tariq, any preferences?

-Toke