linux-kernel - Re: Kernel Linux 2.6.23.16 hangs when run updatedb

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-next>] [day] [month] [year] [list]

Message-ID: <47D54A8B.2020303@mandic.com.br>
Date:	Mon, 10 Mar 2008 11:49:47 -0300
From:	"Renato S. Yamane" <renatoyamane@...dic.com.br>
To:	linux-kernel@...r.kernel.org
CC:	alan-jenkins@...fmail.co.uk, tglx@...utronix.de, devzero@....de,
	mingo@...e.hu
Subject: Re: Kernel Linux 2.6.23.16 hangs when run updatedb

cc'd: Thomas Gleixner
cc'd: Ingo Molnar
About hrtimer comment by Alan Jenkins



Alan Jenkins wrote:
> Renato S. Yamane wrote:
>> devzero@....de wrote:
>>> Renato S. Yamane wrote:
>>>> when cron start updatedb daemon, my machine hangs. None key work, so I
>>>> need reset (press power button to restart).
>>>>
>>>> The only way to get log is runing updatedb from terminal (CTRL + ALT +
>>>> F1) and take a picture from screen:
>>>>
>>>> Up screen:
>>>> <http://img137.imageshack.us/img137/7128/01pg1.jpg>
>>>>
>>>> Down screen:
>>>> <http://img100.imageshack.us/img100/1456/02kx1.jpg>
>>>>
>>>> Call trace detail:
>>>> <http://img100.imageshack.us/img100/8233/calltracedetailsj7.jpg>
>>>
>>>
>>> looks like reiserfs issue.
>>> maybe corrupt filesystem and improper handling of the reiserfs-driver?
>>>
>>> could you try some "find /" ?
>>
>>
>> "find /" don't hangs my machine.
>> The problem is only with updatedb.
>>
>> How can I fix this? Is safe run reiserfsck?
>
> 
> I think he's wrong.
> 
> Looking at the call trace, the BUG happens during an interrupt.  It
> could be a coincidence that the interrupt happened during this
> particular system call.
> 
> It looks like a timer callback has been corrupted / set to an invalid
> value.  The BUG is due to accessing the invalid address 61060fe0
> within enqueue_hrtimer, and the EIP (instruction pointer) is also
> equal to 61060fe0.  This would be consistent with the source code of
> enqueue_hrtimer.  It's not an obvious reiserfs issue.
> 
> I don't know how to find out where this corruption is happening, but
> it's worth asking the hrtimers people.

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