linux-kernel - Re: Reiserfs deadlock in 2.6.36

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: <AANLkTik=+smaiGNwVw0pDBXexVd=trsz9aSawuqLZP6k@mail.gmail.com>
Date:	Wed, 22 Dec 2010 19:11:43 +0100
From:	Bastien ROUCARIES <roucaries.bastien@...il.com>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Reiserfs deadlock in 2.6.36

On Wed, Dec 22, 2010 at 7:04 PM, Frederic Weisbecker <fweisbec@...il.com> wrote:
> On Wed, Dec 22, 2010 at 06:50:48PM +0100, Bastien ROUCARIES wrote:
>> Le jeudi 16 décembre 2010 14:49:48, Bastien ROUCARIES a écrit :
>> > Le jeudi 2 décembre 2010 18:43:32, vous avez écrit :
>> > > On Fri, Nov 26, 2010 at 05:57:05PM +0100, Bastien ROUCARIES wrote:
>> > > > Dear frederic,
>> I achieve to reproduce it. BTW it is my home partition with acl enable
>
> How do you know you reproduced it? You had a crash before using SysRq?
> Or you felt a deadlock or so?
>
> What's interesting is that report is that there is no blocked task
> that holds the reiserfs lock.
>
> So I really feel the problem is that someone opened the journal but did not
> release it.

Could you add a virtual lock for testing this hypothesis ? This lock
will be held during journal opening and releasing during journal
closing, using lockdep for testing this hypothesis ?
>
> How hard is it to reproduce now? If it's not so hard or haphazard, we should
> start a bisection. Otherwise I think we'll need to do some tracing and this
> is going to take several tries :)
>
--
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/