From: Robbie Dinn <robbie@microbus.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] 2.4.23(24?)-2 TT mode hangs on request_module
Date: Mon, 17 May 2004 18:40:18 +0100 [thread overview]
Message-ID: <40A8F902.8090001@microbus.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0405171722530.17607-100000@filer.marasystems.com>
Henrik Nordstrom wrote:
> I can very reliably reproduce the problem by
>
> 1. Boot in single user mode (/proc mounted etc.., but no other disturbing
> factors)
> 2. iptables -A INPUT -j REJECT
>
I think I may have seen this too, although I didn't understand what
was going on at the time (still don't). I am a little unsure what
versions of software I was using, because I wasn't working very
systematically. It might have been:
host: 2.6.6 + skas3 patch or 2.6.6-rc3-mm2 + ska3 patch
+ recent CVS netfilter p-o-m
uml: 2.6.6 + blaisorblades unofficial patches
and/or uml patches from suse kernel
+ recent CVS netfilter p-o-m
I am just a monkey applying patches here, I don't claim to actually
understand the code.
I could get the UML machine to start in single user mode, but
when starting in run level 2 or 3, it would hang (eating lots of cpu
cycles) while starting the firewall.
I assumed that the hang was due to me failing to recompile and install
a fresh version of iptables on UML machine, but I don't have any good
reason to back up that belief. Does that sound plausible?
(I was using iptables-1.2.9 built against an older UML kernel, and had
the 1.2.10 sources waiting to be used).
> The sequence of events here is:
>
> 1. iptables modprobes the base modules (iptable_filter), then uploads the
> new iptable which referes to the REJECT match.
>
> 2. The kernel verifies the new iptable and triggers a request_module call
> for the ipt_REJECT module and here the kernel gets completely stuck..
>
> If all required modules are loaded manually avoiding the call to
> request_module then there is no problem, but unfortunately this is not a
> very feasible workaround here..
>
The UML binary that I was using had all the iptables stuff statically
linked. I wasn't using modules at all.
If by so minor miracle I do manage to assemble something that works or
I find some useful information, I will post a follow up of course.
HTH
Robbie Dinn
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-05-17 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 15:43 [uml-devel] 2.4.23(24?)-2 TT mode hangs on request_module Henrik Nordstrom
2004-05-17 17:40 ` Robbie Dinn [this message]
2004-05-17 18:16 ` Henrik Nordstrom
2004-05-17 21:33 ` Henrik Nordstrom
2004-05-17 22:03 ` Henrik Nordstrom
2004-05-17 23:36 ` [uml-devel] 2.4.26-1 hostfs very broken Henrik Nordstrom
2004-05-18 10:11 ` [uml-devel] [patch] " Henrik Nordstrom
2004-06-02 20:28 ` Jeff Dike
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=40A8F902.8090001@microbus.com \
--to=robbie@microbus.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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