linux-kernel - Re: Oops when read/write or mount/unmount continuously ~ 600.000 times

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

Message-ID: <4895CC61.6040301@gmail.com>
Date:	Sun, 03 Aug 2008 22:18:57 +0700
From:	Hong Tran Duc <hongtd2k@...il.com>
To:	Matthew Wilcox <matthew@....cx>
CC:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	linux-ide@...r.kernel.org
Subject: Re: Oops when read/write or mount/unmount continuously ~ 600.000
 times

Matthew Wilcox wrote:
> On Sun, Aug 03, 2008 at 07:49:50PM +0700, Hong Tran Duc wrote:
>   
>> The reasons is almost linked list on those function was broken. Ex: 
>> linkedlist->next linkedlist->prev = NULL or set to invalid address.
>> In the situation SIGILL, the instruction pointer (NIP) is same as the 
>> return address register (LR).
>>     
>
> In later kernels, we have a list debugging option which lets you find
> list corruptions earlier.
>   
I'm not have much experience with linux kernel architecture, so I don't 
know where I can focus on.

Currently, I'm suspecting these module are affected with this Oops: 
Block I/O management and filesystem, some Wait Queue  ? Is that correct ?
Or would you give me some suggestion what is the most suspicious ? or 
some debugging option you told above ?

Thanks for your help,


-- 
nm.

GPG Key ID: 0xDD253B25
Fingerprint: 2B17 D64A 9561 A443 2ABC 1302 4641 D0B7 DD25 3B25

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