[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201012161449.52318.roucaries.bastien@gmail.com>
Date: Thu, 16 Dec 2010 14:49:48 +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
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,
Sorry for the delay was away internet during my hollidays
> > > Hi Bastien,
> > Nov 26 16:27:56 portablebastien kernel: [27960.811646]
> > [<ffffffff8110142b>] sys_open+0x1b/0x1d Nov 26 16:27:56 portablebastien
> > kernel: [27960.813506] [<ffffffff81009ac2>]
> > system_call_fastpath+0x16/0x1b
>
> Ok, this time I don't have the feeling that a deadlock between reiserfs
> lock and another lock is involved.
>
> We entered queue_log_writer() and then waited for someone to call
> do_journal_end() to testify he finished his job with the journal.
>
> But somehow that didn't happen. Or may be we called queue_log_writer() but
> we shouldn't, thinking there was a writer already but there wasn't. Or
> there is a crazy race somewhere.
>
> On which kernel do you see this?
2.6.36
> Do you know a kernel on which you've never
> seen it.
2.6.34
> Were you running something specific to trigger this deadlock?
>
Nothing specific but it is trigger by kmail reading my mail each time...
Bastien
> Thanks!
--
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/
Powered by blists - more mailing lists