netdev - Re: [PATCH net-next 0/9] net: bcmgenet: start/stop sequence refinement

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: <20171026.101519.1832588976191061738.davem@davemloft.net>
Date:   Thu, 26 Oct 2017 10:15:19 +0900 (KST)
From:   David Miller <davem@...emloft.net>
To:     opendmb@...il.com
Cc:     f.fainelli@...il.com, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 0/9] net: bcmgenet: start/stop sequence
 refinement

From: Doug Berger <opendmb@...il.com>
Date: Wed, 25 Oct 2017 15:04:10 -0700

> This commit set is the result of an investigation into an issue that
> occurred when bringing the interface up and down repeatedly with an
> external 100BASE-T PHY. In some cases the MAC would experience mass
> receive packet duplication that could in rare cases lead to a stall
> from overflow.  The fix for this is contained in the third commit.
> 
> The first 3 commits represent bug fixes that should be applied to the
> net repository and are candidates for backporting to stable releases.
> The remaining commits are enhancements which is why the set is being
> submitted to net-next but they are implemented on top of the fixes.
> 
> The first fix is provided as justification for why the set isn't
> split between a net submission and a net-next submission.

Series applied.

Thanks for fixing up the merge error, I really appreciate that!