From: "Christopher S. Aker" <caker@theshore.net>
To: Paolo Giarrusso <blaisorblade_personal@yahoo.it>
Cc: uml-devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] unable to unmount tmpfs problem lives on
Date: Thu, 16 Dec 2004 18:24:32 -0600 [thread overview]
Message-ID: <001e01c4e3ce$c873fff0$0201a8c0@hawk> (raw)
In-Reply-To: 200412170115.15731.blaisorblade_personal@yahoo.it
> Well, this is yet undiagnosed, but definitely it's not a UML bug... you should
> certainly run a 2.6.8.1 based kernel...
That is unfortunate.
> There is some kind of security bug fixed in 2.6.9, but it was a littler one
> probably (an overflow when handling file position...).
>
> Do you remember when UML crashed and left the unkillable 'D' thread? That's a
> local DoS bug, and this one you're speaking about is a worse one... I and
> Bodo have complained about this one (not on LKML) and didn't get any answer
> yet...
I could try and get a response from LKML, but you would probably present the problem
better...
-Chris
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
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-12-17 0:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 0:05 [uml-devel] unable to unmount tmpfs problem lives on Christopher S. Aker
[not found] ` <200412170115.15731.blaisorblade_personal@yahoo.it>
2004-12-17 0:24 ` Christopher S. Aker [this message]
2004-12-17 0:30 ` Paolo Giarrusso
2004-12-17 3:08 ` Christopher S. Aker
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='001e01c4e3ce$c873fff0$0201a8c0@hawk' \
--to=caker@theshore.net \
--cc=blaisorblade_personal@yahoo.it \
--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