netdev - Re: [net-next PATCH 0/2] NAPI ID fixups related to busy polling

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] [day] [month] [year] [list]

Message-Id: <20170322.112629.1655081687167143481.davem@davemloft.net>
Date:   Wed, 22 Mar 2017 11:26:29 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     alexander.duyck@...il.com
Cc:     netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
        sridhar.samudrala@...el.com, edumazet@...gle.com
Subject: Re: [net-next PATCH 0/2] NAPI ID fixups related to busy polling

From: Alexander Duyck <alexander.duyck@...il.com>
Date: Mon, 20 Mar 2017 14:48:41 -0700

> These two patches are a couple of minor clean-ups related to busy polling.
> The first one addresses the fact that we were trying to busy poll on
> sender_cpu values instead of true NAPI IDs.  The second addresses the fact
> that there were a few paths where TCP sockets were being instanciated based
> on a received patcket, but not recording the hash or NAPI ID of the packet
> that was used to instanciate them.

I'm expecting a respin of this.  Patch #1 appears to be 'net' material, and
Eric asked for some other minor tweaks as well.

Thanks.