netdev - Re: [PATCH net-next 0/6] mlxsw: Add extended ACK for EMADs

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: <20191105.175818.826509723756288899.davem@davemloft.net>
Date:   Tue, 05 Nov 2019 17:58:18 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     jakub.kicinski@...ronome.com
Cc:     idosch@...sch.org, netdev@...r.kernel.org, jiri@...lanox.com,
        shalomt@...lanox.com, mlxsw@...lanox.com, idosch@...lanox.com
Subject: Re: [PATCH net-next 0/6] mlxsw: Add extended ACK for EMADs

From: Jakub Kicinski <jakub.kicinski@...ronome.com>
Date: Tue, 5 Nov 2019 09:54:48 -0800

> Bottom line is I don't like when data from FW is just blindly passed
> to user space. Printing to the logs is perhaps the smallest of this
> sort of infractions but nonetheless if there is no precedent for doing
> this today I'd consider not opening this box.

I agree with Jakub and we should set this kind of precedence.