linux-kernel - Re: [bug] as_merged_requests(): possible recursive locking detected

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080201112238.GN15220@kernel.dk>
Date:	Fri, 1 Feb 2008 12:22:38 +0100
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [bug] as_merged_requests(): possible recursive locking detected

On Fri, Feb 01 2008, Ingo Molnar wrote:
> 
> * Jens Axboe <jens.axboe@...cle.com> wrote:
> 
> > On Fri, Feb 01 2008, Ingo Molnar wrote:
> > > 
> > > * Jens Axboe <jens.axboe@...cle.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?

Right, no bug in lockdep, the locking code and swap_io_context() are
just screwed up.

-- 
Jens Axboe

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/