On Wed, May 21, 2014 at 9:47 PM, David Miller <[email protected]> wrote:
> From: Tom Gundersen <[email protected]>
> Date: Thu, 15 May 2014 23:21:30 +0200
>
>> Enable the module alias hookup to allow tunnel modules to be autoloaded on demand.
>>
>> This is in line with how most other netdev kinds work, and will allow userspace
>> to create tunnels without having CAP_SYS_MODULE.
>>
>> Signed-off-by: Tom Gundersen <[email protected]>
>> ---
>> v2: add ';'
>>
>> Hi Dave,
>>
>> I must have sent out the wrong version of this patch. Sorry for the inconvenience!
>
> Applied to net-next
Thanks!
> although I never saw a firm conclusion in the
> thread for the original patch where there was a discussion about
> whether this is already possible or not.
It is my understanding that this is not already possible, which is why
the MODULE_ALIAS_RTNL_LINK exists.
Would this patch be suitable for stable? While it does not fix a
regression, it appears to fix the intended behaviour of
MODULE_ALIAS_RTNL_LINK?
What I'll do in userspace is to drop CAP_SYS_MODULE and just tell
people who want tunnels to wait for a new kernel (or backport the
patch), but having it in stable would obviously make it simpler.
Cheers,
Tom
From: Tom Gundersen <[email protected]>
Date: Mon, 2 Jun 2014 20:57:02 +0200
> Would this patch be suitable for stable? While it does not fix a
> regression, it appears to fix the intended behaviour of
> MODULE_ALIAS_RTNL_LINK?
It probably is suitable... I'll queue it up, thanks.