linux-kernel - Re: [2.6.31] ir-kbd-i2c oops.

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:	Tue, 29 Sep 2009 16:16:29 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	Paweł Sikora <pluto@...k.net>
Cc:	linux-kernel@...r.kernel.org, linux-i2c@...r.kernel.org,
	LMML <linux-media@...r.kernel.org>
Subject: Re: [2.6.31] ir-kbd-i2c oops.

On Wed, 16 Sep 2009 10:03:32 +0200, Paweł Sikora wrote:
> On Wednesday 16 September 2009 08:57:01 Jean Delvare wrote:
> > Hi Pawel,
> > 
> > I think this would be fixed by the following patch:
> > http://patchwork.kernel.org/patch/45707/
> 
> still oopses. this time i've attached full dmesg.

Any news on this? Do you have a refined list of kernels which have the
bug and kernels which do not? Tried 2.6.32-rc1? Tried the v4l-dvb
repository?

Anyone else seeing this bug?

Your kernel stack trace doesn't look terribly reliable and I am not
able to come to any conclusion. The crash is supposed to happen in
ir_input_init(), but the stack trace doesn't lead there. I am also
skeptical about the +0x64/0x1a52, ir_input_init() is a rather small
function and I fail to see how it could be 6738 bytes in binary size.
Might be that the bug caused a stack corruption. Building a debug
kernel may help.

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