[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpXSv7ddFtF53JGu=QdaNgY7c4O9Wuq4PmVRczTBiE_rSg@mail.gmail.com>
Date: Tue, 5 Feb 2013 18:49:45 +0800
From: Cong Wang <xiyou.wangcong@...il.com>
To: blp@...stanford.edu
Cc: Stephen Hemminger <stephen@...workplumber.org>,
Rusty Russell <rusty@...tcorp.com.au>,
Jesse Gross <jesse@...ira.com>,
"David S. Miller" <davem@...emloft.net>,
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 Tue, Feb 5, 2013 at 2:08 PM, Ben Pfaff <blp@...stanford.edu> wrote:
> Stephen Hemminger <stephen@...workplumber.org> writes:
>
>> On Tue, 29 Jan 2013 22:15:18 +0800
>> Cong Wang <xiyou.wangcong@...il.com> wrote:
>>
>>> 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.
>>
>> Shouldn't the OVS init script be testing for some other API.
>
> I agree that's a bug in the OVS init script. I will fix it.
Thanks for taking care of it, Ben!
--
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