Oskar Andreasson wrote:
> Hi Patrick,
>
> You seem to be right yes, regarding module
loading/handling. I don't
> dare say anything more, but a non-qualified guess is
that it feels like
> some kind of bug between how the UML kernel handles
modules and how
> iptables interact?
Mhh I guess thats rather unlikely, iptables modules do
nothing special.
Any change your /sbin/modprobe is also linked against the
wrong libc
or something like that (and command-line uses
/usr/local/sbin/modprobe)?
> I've attached 3 more scenarios.
>
> 1. just restarted, issuing
> iptables -t nat -A PREROUTING -j DNAT --to 192.168.10.2
> lsmod
> result: kernel panic from lsmod
>
> 2. just restarted, issuing
> iptables -t nat -A POSTROUTING -j MASQUERADE
> lsmod
> result: kernel panic, exactly the same as first
scenario (except for a
> couple of addresses).
>
> 3. just restarted, issuing
> modprobe ipt_MASQUERADE
> modprobe ip_tables
> lsmod
> iptables -t nat -A POSTROUTING -j MASQUERADE
> lsmod
> result: the last lsmod results in a kernel panic.
>
> All modules loaded with modprobe seems to work just
fine, until iptables
> touches them.
>
> I just tried starting an nfs kernel server also, which
didn't seem to
> work either, so it seems mostly like an UML bug. It
crashed at lsmod as
> well.
>
> Would you know which way is the best to get in touch
with the
> uml-people, and how to debug this? My experience with
gdb is ...
> somewhat limited. I guess now is as bad a time as any
to finally sit
> down with it :(. Suggestions on what to read are
welcome.
There's a mailing list at
M: jdike karaya.com
L: user-mode-linux-devel lists.sourceforge.net
L: user-mode-linux-user lists.sourceforge.net
|