mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Alasdair G Kergon <agk@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, dm-devel@redhat.com,
	Andrew Morton <akpm@osdl.org>, Neil Brown <neilb@suse.de>
Subject: Re: 2.6.19-rc6 -- dm: possible recursive locking detected
Date: Mon, 20 Nov 2006 09:49:06 +0100	[thread overview]
Message-ID: <20061120084906.GB17447@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20061117194303.GB4409@agk.surrey.redhat.com>

On Fri, Nov 17, 2006 at 07:43:03PM +0000, Alasdair G Kergon wrote:
> On Fri, Nov 17, 2006 at 04:30:03PM +0100, Heiko Carstens wrote:
> > =============================================
> > [ INFO: possible recursive locking detected ]
> > 2.6.19-rc6-g1b9bb3c1 #28
> > ---------------------------------------------
> > kpartx/945 is trying to acquire lock:
> >  (&md->io_lock){----}, at: [<00000000001f8faa>] dm_request+0x42/0x24c
> > 
> > but task is already holding lock:
> >  (&md->io_lock){----}, at: [<00000000001f8faa>] dm_request+0x42/0x24c
> 
> Known problem - nobody's written a patch to fix it yet to my knowledge,
> but I don't recall any reports of real world lock-ups related to this - just
> several reports of the debug warning messages:-)
> 
> Simply ignore the message for now - or submit a patch that fixes the
> underlying problem:-)

Ignoring would be good, but this problem renders lockdep useless since it
stops working after it found the first possible bug.

While we are at it:

this one is sitting since ages in -mm and probably waiting for your approval:
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc5/2.6.19-rc5-mm2/broken-out/md-dm-reduce-stack-usage-with-stacked-block-devices.patch

      reply	other threads:[~2006-11-20  8:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-17 15:30 Heiko Carstens
2006-11-17 19:43 ` Alasdair G Kergon
2006-11-20  8:49   ` Heiko Carstens [this message]

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=20061120084906.GB17447@osiris.boeblingen.de.ibm.com \
    --to=heiko.carstens@de.ibm.com \
    --cc=agk@redhat.com \
    --cc=akpm@osdl.org \
    --cc=dm-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=neilb@suse.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

all inboxes | Powered by JetHome®