From: "Alexander Y. Fomichev" <gluk@php4.ru>
To: linux-kernel@vger.kernel.org
Cc: Andrea Arcangeli <andrea@suse.de>
Subject: race in expand_stack in 2.6.7 ?
Date: Mon, 26 Jul 2004 19:43:40 +0400 [thread overview]
Message-ID: <200407261943.40472.gluk@php4.ru> (raw)
G'Day.
Some months ago i've reported about bug which Andrea defined as
"race in expand_stack with threads" (http://lkml.org/lkml/2004/4/14/52),
but it was related to -aa branch (More precisely 2.6.5-aa5).
After applied patch from Andrea (many tnx), i did not notice
any troubles with 2.6.5-aa5 and later with 2.6.7 until today
when i've caught very similar bug(?) on the same system.
[Dual P4 Xeon 2.4GHz, 2G ECC RAM - (production web-server)
Gentoo, kernel 2.6.7]
System behaviour and trace are nearly the same, system alive but
i couldn't do ps, pkill etc. Here is a trace:
http://sysadminday.org.ru/expand_stack_race/trace-20040726
config: http://sysadminday.org.ru/expand_stack_race/config-2.6.7
cpuinfo: http://sysadminday.org.ru/expand_stack_race/cpuinfo
lspci: http://sysadminday.org.ru/expand_stack_race/lspci
lspci -vvn http://sysadminday.org.ru/expand_stack_race/lspci-vvn
--
Best regards.
Alexander Y. Fomichev <gluk@php4.ru>
Public PGP key: http://sysadminday.org.ru/gluk.asc
reply other threads:[~2004-07-26 16:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200407261943.40472.gluk@php4.ru \
--to=gluk@php4.ru \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox