From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Subject: schedule_timeout() called with state TASK_RUNNING from fs/select.c
Date: Sat, 7 Jul 2007 15:00:28 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0707071454090.4114@localhost.localdomain> (raw)
as i understand it, schedule_timeout() should always be called with
a current->state of TASK_INTERRUPTIBLE or TASK_UNINTERRUPTIBLE, no?
based on a trivial check i added to kernel/timer.c, i can read this in
/var/log/messages:
...
Jul 7 14:48:40 localhost kernel: Bad schedule_timeout state: 0 from Xorg, c015eeb9
Jul 7 14:49:05 localhost kernel: Bad schedule_timeout state: 0 from gnome-terminal, c015ea47
Jul 7 14:50:19 localhost kernel: Bad schedule_timeout state: 0 from Xorg, c015eeb9
Jul 7 14:50:50 localhost kernel: Bad schedule_timeout state: 0 from Xorg, c015eeb9
...
those last values are __builtin_return_address(0), and here's the
snippet from /proc/kallsyms:
...
c015e7f2 T do_sys_poll
c015eb19 T sys_poll
c015eb50 T do_select
c015ef10 t core_sys_select
...
i'm guessing those addresses correspond to the calls to
schedule_timeout() in do_sys_poll() and do_select(), if anyone thinks
it's worth looking at.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================
next reply other threads:[~2007-07-07 19:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 19:00 Robert P. J. Day [this message]
2007-07-08 11:16 Oleg Nesterov
2007-07-10 7:50 ` Robert P. J. Day
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=Pine.LNX.4.64.0707071454090.4114@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®