netdev - Re: [PATCH net-next v2 0/3] lwtunnel: autoload of lwt modules

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: <20160221.220047.582354891121433128.davem@davemloft.net>
Date:	Sun, 21 Feb 2016 22:00:47 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	rshearma@...cade.com
Cc:	netdev@...r.kernel.org, roopa@...ulusnetworks.com,
	tom@...bertland.com, tgraf@...g.ch, ebiederm@...ssion.com,
	jbenc@...hat.com
Subject: Re: [PATCH net-next v2 0/3] lwtunnel: autoload of lwt modules

From: Robert Shearman <rshearma@...cade.com>
Date: Fri, 19 Feb 2016 09:43:15 +0000

> Changes since v1:
>  - remove "LWTUNNEL_ENCAP_" prefix for the string form of the encaps
>    used when requesting the module to reduce duplication, and don't
>    bother returning strings for lwt modules using netdevices, both
>    suggested by Jiri.
>  - update commit message of first patch to clarify security
>    implications, in response to Eric's comments.
> 
> The lwt implementations using net devices can autoload using the
> existing mechanism using IFLA_INFO_KIND. However, there's no mechanism
> that lwt modules not using net devices can use.
> 
> Therefore, these patches add the ability to autoload modules
> registering lwt operations for lwt implementations not using a net
> device so that users don't have to manually load the modules.

Series applied, thanks.