mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Peter T. Breuer" <ptb@inv.it.uc3m.es>
To: "linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: kernel analyser to detect sleep under spinlock
Date: Sat, 13 Nov 2004 00:45:52 +0100 (MET)	[thread overview]
Message-ID: <200411122345.iACNjqt09561@inv.it.uc3m.es> (raw)
In-Reply-To: From (env: ptb) at "Nov 11, 2004 05:29:40 am"

Peter T. Breuer <ptb (at) inv.it.uc3m.es> writes:
 
> I've added some extra support for gcc 3.4.0 [...]

And now kernel 2.6 files seem to be being parsed OK too.

% ./c -nostdinc -iwithprefix include -D__KERNEL__ -I/usr/local/src/linux-2.6.3/include -D__KERNEL__ -Wall -Wstrict-prototypes -Wno-trigraphs -I/usr/local/src/linux-2.6.3/include/asm-i386/mach-default -O2 -DMODULE -DKBUILD_BASENAME=nbd -DKBUILD_MODNAME=nbd /usr/local/src/linux-2.6.3/drivers/block/nbd.c
*************** sleep calls ************************************
*  function                     line    calls (locks)
*
* - /usr/local/src/linux-2.6.3/include/linux/fs.h
*  lock_super                   741     down (0)
*
* - /usr/local/src/linux-2.6.3/include/net/sock.h
*  sk_filter_release            710     kfree (0)
*
* - /usr/local/src/linux-2.6.3/drivers/block/nbd.c
*  nbd_send_req                 264     down (0)
*  do_nbd_request               510     nbd_send_req (-1)
*  nbd_ioctl                    569     nbd_send_req (-1)
*  nbd_ioctl                    574     down (0)
*
*
* *** found 0 instances of sleep under spinlock ***
*
***************************************************************




Archive at:

   ftp://oboe.it.uc3m.es/pub/Programs/c-1.2.2.tgz


GPL, LGPL, etc.

This is also useful for locating functions which can sleep, though of
course that can be done in other ways.

This utility works by applying a programming logic to the code semantics.
That bit's fine. What it's not so great at is resolving C references back
to the correct declaration, which results in under-reporting. I'll improve
that (mumbles, register actions to be carried out whenever anything
changes in the fact database instead of coding the inferences by hand). 

I'll undertake a survey of the current kernel.

Peter (ptb (at) inv.it.uc3m.es)
 
 



             reply	other threads:[~2004-11-13  0:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-12 23:45 Peter T. Breuer [this message]
2004-11-13 11:09 ` Peter T. Breuer
2004-11-14 15:01   ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2004-11-22 10:06 Peter T. Breuer
2004-11-11  4:29 Peter T. Breuer
2004-11-07 23:14 Peter T. Breuer
2004-11-07 23:14 Peter T. Breuer
2004-11-08  1:18 ` Randy.Dunlap
2004-11-08  4:39   ` Peter T. Breuer
2004-11-08  4:43     ` Randy.Dunlap

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=200411122345.iACNjqt09561@inv.it.uc3m.es \
    --to=ptb@inv.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®