From: Jeff Dike <jdike@addtoit.com>
To: Jiaying Zhang <jiayingz@google.com>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] 2.6.25 uml kernel crashes when it calls down() on a semaphore with zero counter
Date: Mon, 14 Jul 2008 10:46:12 -0400 [thread overview]
Message-ID: <20080714144612.GA5751@c2.user-mode-linux.org> (raw)
In-Reply-To: <5df78e1d0807140206m43291128t32f1489177ad6e3d@mail.gmail.com>
On Mon, Jul 14, 2008 at 05:06:49PM +0800, Jiaying Zhang wrote:
> The 2.6.24 kernels are OK, but I have seen this problem with all of the
> 2.6.25 kernels I have tried. There have been a lot of changes between
> 2.6.24 kernels and 2.6.25 kernels. I am not sure which one may lead
> to this problem.
So bisect it.
> Looks like the problem happens when __down_interruptible is called.
> I checked the semaphore passed to __down_interruptible under gdb
> and found it was corrupted:
> (gdb) f 18
> #18 __down_interruptible (sem=0x9f68d08) at include/linux/list.h:50
> 50 prev->next = new;
> (gdb) p sem
> $15 = (struct semaphore *) 0x9f68d08
> (gdb) p *sem
> $16 = {count = {counter = -268435295}, sleepers = 4, wait = {lock =
> {raw_lock = {<No data fields>}}, task_list = {
> next = 0x9f68d5c, prev = 0x18124}}}
>
> But the semaphore looks correct before calling down_interruptible:
What's the problem with debugging this, then? You step through the
code starting when the semaphore is good and see exactly when it gets
corrupted.
Jeff
--
Work email - jdike at linux dot intel dot com
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
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:[~2008-07-14 14:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 7:53 [SPAM] [uml-devel] 2.6.25 uml kernel crashes when it calls down() on a semaphore with zero counter Jiaying Zhang
2008-07-03 13:56 ` [SPAM] " Jeff Dike
2008-07-04 1:06 ` Jiaying Zhang
2008-07-10 2:25 ` Jiaying Zhang
2008-07-10 17:02 ` Jeff Dike
2008-07-14 9:06 ` Jiaying Zhang
2008-07-14 14:46 ` Jeff Dike [this message]
2008-07-16 9:52 ` Jiaying Zhang
2008-07-17 4:55 ` Jiaying Zhang
2008-07-18 20:53 ` Jeff Dike
2008-07-20 15:20 ` Mattia Dongili
2008-07-20 15:44 ` Jeff Dike
2008-07-21 12:54 ` Mattia Dongili
2008-08-02 5:54 ` Mattia Dongili
2008-08-04 16:44 ` Jeff Dike
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=20080714144612.GA5751@c2.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=jiayingz@google.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