netdev - Re: [PATCH v2 net-next 0/3] net: Allow non-fatal messages to be passed in extack

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: <20171101.115141.825853765204769299.davem@davemloft.net>
Date:   Wed, 01 Nov 2017 11:51:41 +0900 (KST)
From:   David Miller <davem@...emloft.net>
To:     dsahern@...il.com
Cc:     netdev@...r.kernel.org, jiri@...lanox.com, idosch@...lanox.com,
        johannes.berg@...el.com
Subject: Re: [PATCH v2 net-next 0/3] net: Allow non-fatal messages to be
 passed in extack

From: David Ahern <dsahern@...il.com>
Date: Fri, 27 Oct 2017 17:37:11 -0700

> There are many cases where networking subsystems throw non-fatal warning
> messages that end up in dmesg / kernel log to which a user making the
> change is completely oblivious. This set makes the extack facility
> usable for returning such messages.
> 
> The case in point here is spectrum and adding FIB rules which causes an
> offload abort. Make the use case more user friendly by letting the user
> know that offload is no longer happening because of the rule change.
> 
> v2
> - kept the offload abort in a work queue entry per Ido's comment

Series applied, thanks David.