public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [bug] as_merged_requests(): possible recursive locking detected
Date: Fri, 1 Feb 2008 12:01:23 +0100	[thread overview]
Message-ID: <20080201110123.GF27178@elte.hu> (raw)
In-Reply-To: <20080201104733.GM15220@kernel.dk>


* Jens Axboe <jens.axboe@oracle.com> wrote:

> On Fri, Feb 01 2008, Ingo Molnar wrote:
> > 
> > * Jens Axboe <jens.axboe@oracle.com> wrote:
> > 
> > > Are you sure this triggered with the as fixup in place? It looks like 
> > > the same bug.
> > 
> > most definitely a separate bug.
> 
> yeah, I didn't read it carefully enough. Nikanth found the reason.

/me processes his mbox some more and sees the mails

am i right that lockdep complained about real lockup potential here? 
(i.e. it caught a real bug) So there's no need to change anything on the 
lockdep side, right?

	Ingo

  reply	other threads:[~2008-02-01 11:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 22:14 [bug] as_merged_requests(): possible recursive locking detected Ingo Molnar
2008-01-31 22:19 ` Ingo Molnar
2008-02-01  8:40 ` Jens Axboe
2008-02-01 10:45   ` Ingo Molnar
2008-02-01 10:47     ` Jens Axboe
2008-02-01 11:01       ` Ingo Molnar [this message]
2008-02-01 11:22         ` Jens Axboe
     [not found]           ` <47A35177.BANGALORE.BLR.100.174746A.1.1085C.1@1:7.BANGALORE.BLR.100.0.1.0.1@16>
2008-02-01 11:53             ` Fwd: " Nikanth Karthikesan
2008-02-01 10:03 ` Nikanth Karthikesan
2008-02-01 10:12   ` Jens Axboe
2008-02-01 10:31     ` Jens Axboe
2008-02-02  0:54       ` Nick Piggin
2008-02-01 11:00     ` Nikanth Karthikesan

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=20080201110123.GF27178@elte.hu \
    --to=mingo@elte.hu \
    --cc=jens.axboe@oracle.com \
    --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