netdev - Re: [PATCH net-next 0/3] nfp: flower: repr link state

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: <20180103.121825.2053669223295456241.davem@davemloft.net>
Date:   Wed, 03 Jan 2018 12:18:25 -0500 (EST)
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/3] nfp: flower: repr link state

From: Jakub Kicinski <jakub.kicinski@...ronome.com>
Date: Tue,  2 Jan 2018 19:18:58 -0800

> Dirk says:
> 
> This series provides two updates towards the link state of reprs in
> the flower nfp app.
> 
> Patch #1 improves the way link state is reported for reprs. Instead of
> starting with an assumed 'UP' state, always assume the link state is
> 'DOWN' and then modify this only on events received from firmware.
> 
> Patch #2 adds a new nfp_app hook, repr_preclean. This callback is
> executed before reprs are removed from the app context and is executed
> per repr.
> 
> Patch #3 implements the new REIFY control message, used to indicate
> when reprs are created and destroyed. Firmware uses these messages
> to prevent communication about any particular port when the driver
> doesn't know about the repr yet or anymore.

Series applied, thanks.