[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090313151200.1cc16255@nehalam>
Date: Fri, 13 Mar 2009 15:12:00 -0700
From: Stephen Hemminger <shemminger@...ux-foundation.org>
To: David Miller <davem@...emloft.net>
Cc: scott@...onical.com, linux-kernel@...r.kernel.org,
bridge@...ts.linux-foundation.org
Subject: Re: [PATCH 01/31] bridge: Auto-load bridge module when socket
opened.
On Fri, 13 Mar 2009 14:27:18 -0700 (PDT)
David Miller <davem@...emloft.net> wrote:
> From: Scott James Remnant <scott@...onical.com>
> Date: Mon, 2 Mar 2009 16:40:10 +0000
>
> > The bridge module is missing the net-pf-7 alias that would cause it to
> > be auto-loaded when a socket of that type is opened. This patch adds
> > the alias.
> >
> > Signed-off-by: Scott James Remnant <scott@...onical.com>
> > Signed-off-by: Tim Gardner <tim.gardner@...onical.com>
>
> Bridging has no sockets, so this patch won't do anything.
>
> Did you verify that these changes actually do something?
> Or did you blindly run around peppering source files with
> these annotations?
I think this all started when I was debugging a problem where LLC
was not getting autoloaded properly. It turned out that distro's
like Debian (and therefore Ubuntu) had incorrect modprobe.d/alias file
entries. I raised the bug that, "hey you have wrong data and you
really don't need these alias entries at all anymore". There was some
comparison of what was being shipped versus what was in the kernel
and the Debian/Ubuntu guys stepped in to try and unify this.
Let's be supportive of Ubuntu maintainers actually working on upstream
resolution for a change. The normal distro maintainer is "patch and ignore".
In this case, many of these are correct, but several of them are cases
where there is no point in having a module alias because there is no
functiona user visible API. You can try and open a PF_BRIDGE socket, there just
is no point.
--
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