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: <AANLkTinp4=c9qmVyfocUk_ydJ3PV50b9UckNhJJNFsFm@mail.gmail.com>
Date:	Tue, 8 Mar 2011 16:22:59 +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 Tue, Mar 8, 2011 at 3:18 PM, Frederic Weisbecker <fweisbec@...il.com> wrote:
> On Sun, Jan 30, 2011 at 01:08:29AM +0100, Bastien ROUCARIES wrote:
>> Le jeudi 23 décembre 2010 04:42:33, Frederic Weisbecker a écrit :
>> Hi,
>>
>> I take me more than two days of testing to reporduce this bugs with trace enabled. My filesystem was quite slow and this bugs seems
>> to be timing related.
>>
>> One patern that trigger this bug is git. Doing a lot of git work of my desktop crash my machine.
>>
>> Moreover, trying to reproduce this bug lead to data loss. I have rebuilded twice my / partition using --rebuild-tree, and restored
>> my home partition three times using backups.
>>
>> My log is here.
>>
>> Do you need more information?
>>
>> Bastien
>
> You have a first series of hung task report from 19440.852298 to 19440.880024
> then it's followed by the traces and then again with a hung task report at
> 19560.880084. But there is only one task stuck in that 2nd report. Did
> you report your whole dmesg there or have you cut it? If it's your
> whole dmesg then it means the other tasks from the first report have released
> from their hung state. So the queued writers have been released by someone
> who closed the journal.

I have reported the whole stuff. But because my log need to go to my
disk, we could have loss something

> This could confirm the theory that someone has opened the journal and
> spent way too much time before releasing it. Or something else.
> In any case tell me, there are other tests we can run.
>

Ok bastien
--
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/