[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpWOKTrG2_8NVTd73AvLt3mcYGLisSTdHprStQ=dABSVgQ@mail.gmail.com>
Date: Tue, 5 Feb 2013 22:28:27 +0800
From: Cong Wang <xiyou.wangcong@...il.com>
To: Rusty Russell <rusty@...tcorp.com.au>
Cc: Jesse Gross <jesse@...ira.com>,
"David S. Miller" <davem@...emloft.net>, Greg KH <greg@...ah.com>,
LKML <linux-kernel@...r.kernel.org>,
Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: No sysfs directory for openvswitch module when built-in
On Mon, Feb 4, 2013 at 1:59 PM, Rusty Russell <rusty@...tcorp.com.au> wrote:
> Cong Wang <xiyou.wangcong@...il.com> writes:
>> Hello, Rusty, Jesse,
>>
>> I met an interesting problem when I compile openvswitch module as a
>> built-in (actually I compile ALL kernel modules as built-in), there is
>> no /sys/module/openvswitch/ directory created by the kernel in this
>> case.
> ...
>> What's worse, the user-space init script thinks openvswitch module is
>> not loaded by checking the exist of this directory, therefore refuses
>> to start.
>
> We only know built-in "modules" exist if we see a parameter or version
> which mention them. Looking for /sys/module/openvswitch/ is almost as
> flawed as looking in /proc/modules.
You are right. Ben will fix the openvswitch init script.
Thanks for your reply!
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists