From: "joshua dot i dot stone at intel dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/6487] kernel.function("internal_add_timer") freezes system.
Date: Wed, 07 May 2008 20:22:00 -0000 [thread overview]
Message-ID: <20080507184818.26629.qmail@sourceware.org> (raw)
In-Reply-To: <20080507143402.6487.mhiramat@redhat.com>
------- Additional Comments From joshua dot i dot stone at intel dot com 2008-05-07 18:48 -------
It's just a coincidence that the first mod_timer was also from stap. There's a
real bug here: a probe on the internals of __mod_timer will call
stp_print_flush, and if the buffer is full it will end up calling __mod_timer
again and cause a deadlock.
relay_switch_subbuf has this note:
> /*
> * Calling wake_up_interruptible() from here
> * will deadlock if we happen to be logging
> * from the scheduler (trying to re-grab
> * rq->lock), so defer it.
> */
> __mod_timer(&buf->timer, jiffies + 1);
... but in this case we happen to be logging from within __mod_timer, so it's a
new deadlock.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=6487
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2008-05-07 18:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 18:37 [Bug runtime/6487] New: " mhiramat at redhat dot com
2008-05-07 18:45 ` [Bug runtime/6487] " mhiramat at redhat dot com
2008-05-07 18:48 ` mhiramat at redhat dot com
2008-05-07 18:55 ` mhiramat at redhat dot com
2008-05-07 20:22 ` joshua dot i dot stone at intel dot com [this message]
2008-05-07 20:52 ` fche at redhat dot com
2008-05-07 21:28 ` fche at redhat dot com
2008-05-07 22:50 ` mhiramat at redhat dot com
2008-05-07 23:37 ` mhiramat at redhat dot com
2008-05-10 14:27 ` fche at redhat dot com
2008-05-12 13:11 ` fche at redhat dot com
2008-05-13 6:08 ` fche at redhat dot com
2008-05-16 18:57 ` mhiramat at redhat dot com
2008-09-17 19:21 ` fche at redhat dot com
2008-09-17 19:22 ` fche at redhat dot com
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=20080507184818.26629.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).