linux-kernel - Re: [PATCH net-next] net/ncsi: Don't take any action on HNCDSC AEN

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 15 Dec 2017 14:06:45 +0800
From:   Jeremy Kerr <jk@...abs.org>
To:     Samuel Mendoza-Jonas <sam@...dozajonas.com>, netdev@...r.kernel.org
Cc:     openbmc@...ts.ozlabs.org, "David S . Miller" <davem@...emloft.net>,
        linux-kernel@...r.kernel.org, Brian J King <bjking1@...ibm.com>
Subject: Re: [PATCH net-next] net/ncsi: Don't take any action on HNCDSC AEN

Hi Sam,

> The current HNCDSC handler takes the status flag from the AEN packet and
> will update or change the current channel based on this flag and the
> current channel status.
> 
> However the flag from the HNCDSC packet merely represents the host link
> state. While the state of the host interface is potentially interesting
> information it should not affect the state of the NCSI link. Indeed the
> NCSI specification makes no mention of any recommended action related to
> the host network controller driver state.

Yep, sounds good to me. If the link status does change, we should see an
separate AEN for that event.

Acked-by: Jeremy Kerr <jk@...abs.org>

However: we're looking at some behaviour of Broadcom NICs at the moment,
where the phy will be reset on link change events. We'd want to make
sure that we're not just seeing the HNCDSC events for that too. I'd
suggest we also get an Ack from Brian (CCed) to make sure we're not
breaking that case.

Cheers,


Jeremy