From: Arjan van de Ven <arjan@linux.intel.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org
Subject: Re: linux-next - request_module_nowait() breaks iptables and iwl3945
Date: Tue, 17 Mar 2009 21:59:02 -0700 [thread overview]
Message-ID: <49C07F96.2070306@linux.intel.com> (raw)
In-Reply-To: <200903181442.16570.rusty@rustcorp.com.au>
Rusty Russell wrote:
> On Wednesday 18 March 2009 08:57:15 Valdis.Kletnieks@vt.edu wrote:
>> On Tue, 17 Mar 2009 16:27:58 +1030, Rusty Russell said:
>>> On Monday 16 March 2009 12:28:04 Valdis.Kletnieks@vt.edu wrote:
>>>> On recent linux-next, iptables and iwl3945 would fail to load
>>> Please send .config; I can't reproduce this here.
>> [root@turing-police ~]# /etc/init.d/iptables start
>> iptables: Applying firewall rules:
>> iptables-restore v1.4.2: iptables-restore: unable to initialize table 'filter'
>
> OK, I think this might fix it. It's already queued, but was labelled a mere
> "cleanup".
I wouldn't understand how it would fix it though;
the code before my patch passes in a 1, and the code after my patch passes in a variable
which has the value 1 as well.... using a symbolic name for it instead isn't going
to impact the generated code afaics...
next prev parent reply other threads:[~2009-03-18 4:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 1:58 linux-next - request_module_nowait() breaks iptables and iwl3945 Valdis.Kletnieks
2009-03-16 15:37 ` Arjan van de Ven
2009-03-17 5:57 ` Rusty Russell
2009-03-17 22:27 ` Valdis.Kletnieks
2009-03-18 4:12 ` Rusty Russell
2009-03-18 4:59 ` Arjan van de Ven [this message]
2009-03-18 23:39 ` Rusty Russell
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=49C07F96.2070306@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox