netdev - Re: [PATCH net] nfp: do not update MTU from BH in flower app

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]

Date:   Fri, 11 Aug 2017 10:10:24 +0200
From:   Simon Horman <horms@...ge.net.au>
To:     Simon Horman <simon.horman@...ronome.com>
Cc:     David Miller <davem@...emloft.net>,
        Jakub Kicinski <jakub.kicinski@...ronome.com>,
        netdev@...r.kernel.org, oss-drivers@...ronome.com
Subject: Re: [PATCH net] nfp: do not update MTU from BH in flower app

On Fri, Aug 11, 2017 at 10:07:03AM +0200, Simon Horman wrote:
> The Flower app may receive a request to update the MTU of a representor
> netdev upon receipt of a control message from the firmware. This requires
> the RTNL lock which needs to be taken outside of the packet processing
> path.
> 
> As a handling of this correctly seems a little to invasive for a fix simply
> skip setting the MTU for now.

Sorry, please ignore this.

It is not against net as it claims. I will post a version against that tree.