netdev - Re: [PATCH net-next 00/15] eth: fbnic: support queue API and zero-copy Rx

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: <CAHS8izMHOzC2MUqZWgcQksLkTW_D7MJ4mndozA4pyfwAPzw0vQ@mail.gmail.com>
Date: Thu, 21 Aug 2025 08:22:27 -0700
From: Mina Almasry <almasrymina@...gle.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Taehee Yoo <ap420073@...il.com>, Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org, 
	edumazet@...gle.com, andrew+netdev@...n.ch, horms@...nel.org, 
	michael.chan@...adcom.com, tariqt@...dia.com, dtatulea@...dia.com, 
	hawk@...nel.org, ilias.apalodimas@...aro.org, alexanderduyck@...com, 
	sdf@...ichev.me, davem@...emloft.net
Subject: Re: [PATCH net-next 00/15] eth: fbnic: support queue API and
 zero-copy Rx

On Thu, Aug 21, 2025 at 8:03 AM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Thu, 21 Aug 2025 23:53:37 +0900 Taehee Yoo wrote:
> > > I haven't looked closely either :) but my gut feeling is that this
> > > is because the devmem test doesn't clean up after itself. It used to
> > > bail out sooner, with this series is goes further in messing up the
> > > config, and then all tests that run after have a misconfigured NIC..
> > >
> > > Taehee, are you planning to work on addressing that? I'm happy to fix
> > > it up myself, if you aren't already half way done with the changes
> > > yourself, or planning to do it soon..
> >
> > Apologies for the delayed action.
> > I would appreciate it if you could address this issue.
>
> Will do, thanks!
>
> Let me apply the first patch of this series, and the rest has to wait
> until I fix the devmem test, I guess.

I'll take a look.

...although I happen to be running into a random machine capacity
issue at the moment. I hope to resolve that sometime this week and
look into this.

-- 
Thanks,
Mina