From: Ben Pfaff <blp@cs.stanford.edu>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Cong Wang <xiyou.wangcong@gmail.com>,
Rusty Russell <rusty@rustcorp.com.au>,
Jesse Gross <jesse@nicira.com>,
"David S. Miller" <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: No sysfs directory for openvswitch module when built-in
Date: Mon, 04 Feb 2013 22:08:13 -0800 [thread overview]
Message-ID: <87lib3gunm.fsf@blp.benpfaff.org> (raw)
In-Reply-To: <20130204081920.00e9f22e@nehalam.linuxnetplumber.net> (Stephen Hemminger's message of "Mon, 4 Feb 2013 08:19:20 -0800")
Stephen Hemminger <stephen@networkplumber.org> writes:
> On Tue, 29 Jan 2013 22:15:18 +0800
> Cong Wang <xiyou.wangcong@gmail.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.
next prev parent reply other threads:[~2013-02-05 6:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 14:15 No sysfs directory for openvswitch module when built-in Cong Wang
2013-02-04 5:59 ` Rusty Russell
2013-02-05 14:28 ` Cong Wang
2013-02-05 17:59 ` Ben Hutchings
2013-02-06 23:38 ` Rusty Russell
2013-02-04 16:19 ` Stephen Hemminger
2013-02-05 6:08 ` Ben Pfaff [this message]
2013-02-05 10:49 ` Cong Wang
2013-02-05 19:15 ` Ben Pfaff
2013-02-05 22:11 ` Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lib3gunm.fsf@blp.benpfaff.org \
--to=blp@cs.stanford.edu \
--cc=davem@davemloft.net \
--cc=jesse@nicira.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=stephen@networkplumber.org \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.