linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Richard Andrews <bbmaj7@yahoo.com.au>, Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] [uml-user] Hanging using 'iptables -L' in UML vm booted with con0=pts
Date: Tue, 11 Sep 2007 16:06:08 +0200	[thread overview]
Message-ID: <200709111606.08509.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20070910155943.GA14112@c2.user-mode-linux.org>


[-- Attachment #1.1: Type: text/plain, Size: 934 bytes --]

On lunedì 10 settembre 2007, Jeff Dike wrote:
> On Wed, Sep 05, 2007 at 09:00:51AM +1000, Richard Andrews wrote:
> > There is an outstanding kernel + mod_utils bug I am tracking via RedHat
> > that exhibits similar behaviour - lockup with 100% CPU in modprobe.
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=212922
>
> This one seems not to have anything to do with UML, while the bug that
> we're talking about here seems to, as modprobe sometimes works and
> sometimes doesn't.

My memory remembers that vmalloc() is used both by iptables and by module 
support, and that I've learnt this while we debugged some very old vmalloc 
bug (I may be talking of 2.4.20). I've not had the time to look at that 
report, but does what I say make sense to you?
-- 
"Doh!" (cit.), I've made another mistake!
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 194 bytes --]

_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2007-09-11 14:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <46DDAD83.4030004@cttc.es>
     [not found] ` <20070904214521.GB5417@c2.user-mode-linux.org>
     [not found]   ` <296838.33596.qm@web52009.mail.re2.yahoo.com>
2007-09-10 15:59     ` [uml-devel] [uml-user] Hanging using 'iptables -L' in UML vm booted with con0=pts Jeff Dike
2007-09-11 14:06       ` Blaisorblade [this message]
     [not found]   ` <46DE8F70.4070404@cttc.es>
     [not found]     ` <20070910160238.GC14112@c2.user-mode-linux.org>
     [not found]       ` <46E71F58.6050301@cttc.es>
     [not found]         ` <46E85FA0.9040405@cttc.es>
2007-09-12 20:30           ` Jeff Dike
2007-09-13  0:59             ` Fermín Galán Márquez
2007-09-13 17:08               ` Blaisorblade
2007-09-13 21:14                 ` [uml-devel] (Solved) " Fermín Galán Márquez
2007-09-18 15:06                   ` [uml-devel] (Workarounded) " Paolo Giarrusso
2007-09-19 19:42                     ` Fermín Galán Márquez
2007-10-10 14:21                       ` David Fernández

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=200709111606.08509.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=bbmaj7@yahoo.com.au \
    --cc=jdike@addtoit.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