linux-kernel - Re: 2.6.22-rc6-mm1 -- BUG - EIP: [<c01a77a1>] sysfs_addrm

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]

Date:	Wed, 11 Jul 2007 18:48:25 +0900
From:	Tejun Heo <htejun@...il.com>
To:	Miles Lane <miles.lane@...il.com>
CC:	Andrew Morton <akpm@...l.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.22-rc6-mm1 -- BUG - EIP: [<c01a77a1>] sysfs_addrm_finish+0x1c2/0x226
 SS:ESP 0068:c5ff9db8

Tejun Heo wrote:
> Miles Lane wrote:
>>> Thanks a lot.  Just in case, if you remove the patch (patch -R -p1), the
>>> oops goes away, right?
>> I double-checked.  I can boot fine after building without your patch.
>> Also, I reproduced the initial BUG I reported (triggered by
>> "modprobe -r ipw2200").
> 
> This is creepy.  I was able to reproduce the oops here with your
> configuration file and making buffers for kallsyms static solved the
> problem.  It isn't stack overflow.  At maximum those arrays added 254
> bytes to the stack and when the oops occurs stack area was left more
> than enough.  I'll keep looking into why that happened but the attached
> patch should get us going on the original subject.

Alright, found out what was going on.  KSYM_NAME_LEN doesn't include
space for the trailing '\0'.  Gees, I've read enough assembly for the
month to find that out.  Anyways, here's proper debug patch.

Thanks.

-- 
tejun

View attachment "debug" of type "text/plain" (4488 bytes)