public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Arjan van de Ven <arjan@infradead.org>,
	Andrew Morton <akpm@osdl.org>, Miles Lane <miles.lane@gmail.com>,
	linux1394-devel@lists.sourceforge.net,
	LKML <linux-kernel@vger.kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: 2.6.18-rc5-mm1 + all hotfixes -- INFO: possible	recursive	locking detected
Date: Wed, 6 Sep 2006 02:10:10 +0200	[thread overview]
Message-ID: <20060906001010.GN9173@stusta.de> (raw)
In-Reply-To: <44FDF9BC.1000403@s5r6.in-berlin.de>

On Wed, Sep 06, 2006 at 12:27:08AM +0200, Stefan Richter wrote:
> Arjan van de Ven wrote:
> > On Tue, 2006-09-05 at 21:23 +0200, Stefan Richter wrote:
> >> This information confuses me. These places are not supposed to be the
> >> ones where the locks were actually acquired, are they?
> > 
> > they should be yes
> > (but inlined functions get the name of the function they are inlined
> > into)
> 
> Was there function inlining performed? E.g. on those functions that are
> called from only one place?

If a static function has only one caller it gets inlined.

> Stefan Richter

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-09-06  0:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-05 17:37 2.6.18-rc5-mm1 + all hotfixes -- INFO: possible recursive locking detected Miles Lane
2006-09-05 18:13 ` Andrew Morton
2006-09-05 18:16   ` Miles Lane
2006-09-05 19:03     ` Stefan Richter
2006-09-05 19:19       ` Miles Lane
2006-09-05 19:51         ` Stefan Richter
2006-09-05 19:23   ` Stefan Richter
2006-09-05 21:07     ` Arjan van de Ven
2006-09-05 22:27       ` Stefan Richter
2006-09-06  0:10         ` Adrian Bunk [this message]
2006-09-06  7:13     ` Stefan Richter
2006-09-06 16:50       ` Stefan Richter
2006-09-06 17:04         ` [RFT PATCH 1/2] ieee1394: nodemgr: fix rwsem recursion Stefan Richter
2006-09-06 17:06           ` [RFT PATCH 2/2] ieee1394: nodemgr: grab class.subsys.rwsem in nodemgr_resume_ne Stefan Richter
2006-09-07 22:45         ` 2.6.18-rc5-mm1 + all hotfixes -- INFO: possible recursive locking detected Miles Lane
2006-09-07 23:23           ` Stefan Richter
2006-09-06 22:35       ` Greg KH
2006-09-05 19:49   ` Miles Lane
2006-09-05 20:19     ` Stefan Richter
2006-09-05 20:26       ` Stefan Richter
2006-09-05 20:33       ` Andrew Morton
2006-09-06  6:39 ` Arjan van de Ven

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=20060906001010.GN9173@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=miles.lane@gmail.com \
    --cc=stefanr@s5r6.in-berlin.de \
    /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