netdev - Re: [PATCH next-next 0/4] rtnetlink: rework handler (un)registering

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: <20171204.115757.1176520446961809221.davem@davemloft.net>
Date:   Mon, 04 Dec 2017 11:57:57 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     fw@...len.de
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH next-next 0/4] rtnetlink: rework handler (un)registering

From: Florian Westphal <fw@...len.de>
Date: Mon, 4 Dec 2017 17:53:04 +0100

> The only difference is that theoretically some addrlabel rtnetlink
> ops are not available if registration fails, but thats not really worse
> than before as this used to panic() instead :-)
> 
> I can send a followup patch, to convert all of ipv6, should be easy
> to propagate errors from addrlabel initialisation to its callsite.

Yes, please make ipv6 consistent in this area when you get a chance.

Thanks.