linux-kernel - Re: [PATCH 1/2] net: ethernet: bgmac: init sequence bug

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

Message-ID: <efd17b6863565d63b37b1bf75082d7b9@milecki.pl>
Date:   Thu, 02 Feb 2017 21:15:51 +0100
From:   Rafał Miłecki <rafal@...ecki.pl>
To:     Zac Schroff <zachary.schroff@...adcom.com>
Cc:     Jon Mason <jon.mason@...adcom.com>,
        David Miller <davem@...emloft.net>,
        bcm-kernel-feedback-list@...adcom.com, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org, Zac Schroff <zschroff@...adcom.com>
Subject: Re: [PATCH 1/2] net: ethernet: bgmac: init sequence bug

On 2017-02-02 01:31, Zac Schroff wrote:
> How about BCMA_IOCTL_PRESERVE_ACROSS_INIT?

I think wireless drivers may still set some these bits during init.

I've a simpler idea: make it bgmac specific. Call it sth like
BGMAC_BCMA_IOCTL_PRESERVE
BGMAC_BCMA_IOCTL_RESERVED
BGMAC_BCMA_IOCTL_DONT_TOUCH