From: Pavel Machek <pavel@ucw.cz>
To: John Byrne <john.l.byrne@hp.com>
Cc: Linus Torvalds <torvalds@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Still a mm bug in the fork error path
Date: Sun, 17 Oct 2004 22:26:52 +0200 [thread overview]
Message-ID: <20041017202652.GF7476@elf.ucw.cz> (raw)
In-Reply-To: <416CA0B1.20900@hp.com>
Hi!
> In my kernel, it was a SIGKILL to a forking kernel thread that caused
> the problem. While I see SIGKILLs being sent to some kernel threads, I
> don't know if any of the kernel threads ever fork. If they don't,
> barring a demented root user sending SIGKILLs to kernel threads, I don't
> know if anyone else will ever see this. So, I don't have any problems
> with it being fixed post 2.6.9.
Actually I do not think that root sending SIGKILLs to kernel threads
is demented... I tried to recover broken machine by SIGKILLing
kacpid. It did not work, so I just reniced it to get machine back.
Pavel
PS: BTW it was evo n620c. There's something wrong with thermal
handling after swsusp. Evo will not die by overheat, but it almost
damaged machine it was standing on... ouch. Cover got deformed by
heat (quite a bit), fortunately it returned to previous shape when it
cooled down.
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
prev parent reply other threads:[~2004-10-17 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 23:30 [PATCH] Still a mm bug in the fork error path John Byrne
2004-10-13 2:09 ` Linus Torvalds
2004-10-13 3:27 ` John Byrne
2004-10-14 4:21 ` Linus Torvalds
2004-10-17 20:26 ` Pavel Machek [this message]
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=20041017202652.GF7476@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=john.l.byrne@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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.