From: "Peter T. Breuer" <ptb@it.uc3m.es>
To: linux kernel <linux-kernel@vger.kernel.org>
Subject: sleep under spinlock detection
Date: Thu, 5 Jun 2003 14:05:09 +0200 (MET DST) [thread overview]
Message-ID: <200306051205.h55C5At08035@oboe.it.uc3m.es> (raw)
I've put a prototype c-code analyser on the net at
ftp://oboe.it.uc3m.es/pub/Programs/c-1.0.tgz
It currently is only detecting sleep under spinlock (and needs another
pass to do it with full accuracy). But it's a start. I've run it over
about 28KLOC so far.
% ./c -D__KERNEL__ -DMODULE -I/usr/local/src/linux-2.4.17rc2-xfs/include ../dbr/1/sbull.c
gcc -D__KERNEL__ -DMODULE -I/usr/local/src/linux-2.4.17rc2-xfs/include -E ../dbr/1/sbull.c -o .gcc-nM5VVc
eek! index 353 has no key in db
can't find key 353!
eek! index 352 has no key in db
can't find key 352!
eek! index 352 has no key in db
can't find key 352!
eek! index 352 has no key in db
can't find key 352!
smb_lock_server is sleepy because it calls down.4605
lock_parent is sleepy because it calls down.6287
double_down is sleepy because it calls down.6310
triple_down is sleepy because it calls down.6340
double_lock is sleepy because it calls double_down.6358
lock_super is sleepy because it calls down.9463
sbull_ioctl is sleepy because it calls interruptible_sleep_on.10021
***
*** sleep under spinlock at file="../dbr/1/sbull.c" about line=420
***
sbull_request is sleepy because it calls interruptible_sleep_on.10182
sbull_init is sleepy because it calls kfree.10244
sbull_cleanup is sleepy because it calls kfree.10264
Peter
next reply other threads:[~2003-06-05 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 12:05 Peter T. Breuer [this message]
2003-06-05 13:13 ` Dave Jones
2003-06-05 13:56 Peter T. Breuer
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=200306051205.h55C5At08035@oboe.it.uc3m.es \
--to=ptb@it.uc3m.es \
--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
all inboxes | Powered by JetHome®