From: Krister Johansen <kjlx@templeofstupid.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [PATCH net] Panic when tc_lookup_action_n finds a partially initialized action.
Date: Tue, 11 Oct 2016 02:28:05 -0700 [thread overview]
Message-ID: <20161011092805.GA7837@templeofstupid.com> (raw)
In-Reply-To: <CAM_iQpUya1ORUUNC9-spLKHjsjNyj6xHO79kvoDGaZcWT_mEwg@mail.gmail.com>
On Wed, Oct 05, 2016 at 11:01:38AM -0700, Cong Wang wrote:
> Does the attached patch make any sense now? Our pernet init doesn't
> rely on act_base, so even we have some race, the worst case is after
> we initialize the pernet netns for an action but its ops still not
> visible, which seems fine (at least no crash).
I tried to reproduce the panic with this latest patch, but I am unable
to do so. The one difference I notice between this patch, and the one I
sent to the list, is that with yours it takes much longer before we get
any output from the simultaneous launch of these containers. Presumably
that's the extra latency added by allowing many extra modprobe calls to
get spawned by request_module().
-K
next prev parent reply other threads:[~2016-10-11 9:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-02 3:13 [PATCH net] Panic when tc_lookup_action_n finds a partially initialized action Krister Johansen
2016-10-03 1:18 ` Jamal Hadi Salim
2016-10-04 6:38 ` Krister Johansen
2016-10-03 18:22 ` Cong Wang
2016-10-04 6:39 ` Krister Johansen
2016-10-05 6:52 ` Krister Johansen
2016-10-05 18:01 ` Cong Wang
2016-10-05 18:07 ` Cong Wang
2016-10-06 6:11 ` Krister Johansen
2016-10-06 19:01 ` Cong Wang
2016-10-09 6:13 ` Krister Johansen
2016-10-11 17:36 ` Cong Wang
2016-10-11 9:28 ` Krister Johansen [this message]
2016-10-11 17:51 ` Cong Wang
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=20161011092805.GA7837@templeofstupid.com \
--to=kjlx@templeofstupid.com \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.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.