[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAG-2HqUEqz26YMTDHNVHUEtWDcaVrq3EKX-e8-9wnm4Y1XCUag@mail.gmail.com>
Date: Mon, 2 Jun 2014 20:57:02 +0200
From: Tom Gundersen <teg@...m.no>
To: David Miller <davem@...emloft.net>
Cc: netdev <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Patrick McHardy <kaber@...sh.net>, yoshfuji@...ux-ipv6.org,
jmorris@...ei.org, Alexey Kuznetsov <kuznet@....inr.ac.ru>
Subject: Re: [PATCH v2] net: tunnels - enable module autoloading
On Wed, May 21, 2014 at 9:47 PM, David Miller <davem@...emloft.net> wrote:
> From: Tom Gundersen <teg@...m.no>
> 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 <teg@...m.no>
>> ---
>> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists