netdev - Re: [PATCH net-next 0/6] nfp: refactor app init, and minor flower fixes

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: <20170903.212221.1440891147611396315.davem@davemloft.net>
Date:   Sun, 03 Sep 2017 21:22:21 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     jakub.kicinski@...ronome.com
Cc:     netdev@...r.kernel.org, oss-drivers@...ronome.com
Subject: Re: [PATCH net-next 0/6] nfp: refactor app init, and minor flower
 fixes

From: Jakub Kicinski <jakub.kicinski@...ronome.com>
Date: Sat,  2 Sep 2017 18:25:59 -0700

> This series is a part 2 to what went into net as a simpler fix.
> In net we simply moved when existing callbacks are invoked to
> ensure flower app does not still use representors when lower 
> netdev has already been destroyed.  In this series we add a
> callback to notify apps when vNIC netdevs are fully initialized
> and they are about to be destroyed.  This allows flower to spawn
> representors at the right time, while keeping the start/stop
> callbacks for what they are intended to be used - FW initialization
> over control channel.
> 
> Patch 4 improves drop monitor interaction and patch 5 changes 
> the default Kconfig selection of flower offload.  Patch 6 fixes
> locking around representor updates which got lost in net-next.

Series applied, thanks.