All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@bytesex.org>
To: Armin.Warda@gmx.De
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: UML fills /tmp irreversibly (2.6.9-bb4 on SuSE 9.2)
Date: 07 Jan 2005 12:20:15 +0100	[thread overview]
Message-ID: <87wtup8p00.fsf@bytesex.org> (raw)
In-Reply-To: <200501051522.52632.Armin.Warda@gmx.de>

"Armin M. Warda" <Armin.Warda@gmx.de> writes:

> On Wednesday 05 January 2005 12:28, Gerd Knorr wrote:
> > > > # mount tmpfs tmp/ -t tmpfs
> > > > # TMPDIR=./tmp/ /kernels/non-fix-kill-patched-kernel
> > > > rootfs=debian.fs # uml_mconsole .uml/xxx/mconsole cad
> > > > # kill -KILL <pid1> <pid2>
> >
> > That doesn't kill all the processes, I additionally need 'kill
> > -CONT' for one of them.
> 
> I remember that behaviour you describe from the uml-kernel that was 
> delivered on SuSE 9.2's Distribution media, um-host-kernel-2.6.8-24.* 
> 
> But my 2.6.9-bb4 um-kernel does not show that problem, I think because 
> bb4 has that fix-kill patch inside.

Yep, but without the fix-kill patch it's reporty easier to trigger.  I
still can't reproduce it on my machine though for some reason, hints
very welcome.  It happens to me only when some uml process still hangs
around, and after killing it off I can umount the filesystem just fine.

  Gerd

-- 
#define printk(args...) fprintf(stderr, ## args)


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
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:[~2005-01-07 11:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-14  8:58 [uml-devel] UML fills /tmp irreversibly (2.6.9-bb4 on SuSE 9.2) Armin M. Warda
2004-12-16 14:50 ` [uml-devel] " Armin M. Warda
     [not found] ` <20041216183604.GB24982@bytesex>
     [not found]   ` <200412162013.21197.blaisorblade_personal@yahoo.it>
2004-12-30 14:20     ` Armin M. Warda
2004-12-30 16:14       ` Christopher S. Aker
2004-12-31 11:22         ` Armin M. Warda
2005-01-01 20:10           ` Christopher S. Aker
2005-01-02  9:25             ` Armin M. Warda
2005-01-03 14:07               ` Armin M. Warda
2005-01-03 10:13       ` Gerd Knorr
2005-01-03 11:49         ` Armin M. Warda
     [not found]           ` <20050103133412.GA25262@bytesex>
2005-01-03 14:31             ` Armin M. Warda
2005-01-04 11:59               ` Gerd Knorr
2005-01-04 14:05                 ` Armin M. Warda
2005-01-04 14:39                   ` Gerd Knorr
2005-01-04 15:33                     ` Christopher S. Aker
2005-01-05 11:28                       ` Gerd Knorr
2005-01-05 14:22                         ` Armin M. Warda
2005-01-07 11:20                           ` Gerd Knorr [this message]
2005-01-04 14:52                   ` Michael Richardson
2005-01-08 12:15               ` Paolo Giarrusso
2005-01-10 13:10                 ` Gerd Knorr
     [not found] ` <200501101450.32169.Armin.Warda@gmx.de>
     [not found]   ` <20050111165848.GA20592@bytesex>
2005-01-12 15:53     ` Armin M. Warda
2005-01-17 15:26       ` Gerd Knorr

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=87wtup8p00.fsf@bytesex.org \
    --to=kraxel@bytesex.org \
    --cc=Armin.Warda@gmx.De \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.