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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20091001124210.4be1dd71@hyperion.delvare>
Date:	Thu, 1 Oct 2009 12:42:10 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	Paweł Sikora <pluto@...k.net>
Cc:	"Andy Walls" <awalls@...ix.net>, linux-kernel@...r.kernel.org,
	LMML <linux-media@...r.kernel.org>
Subject: Re: [2.6.31] ir-kbd-i2c oops.

On Thu, 01 Oct 2009 12:17:20 +0200, Paweł Sikora wrote:
> Dnia 01-10-2009 o 12:06:09 Jean Delvare <khali@...ux-fr.org> napisał(a):
> 
> >> I'm not sure if it is the problem here, but it may be prudent to check
> >> that there's no mismatch between the module and the structure
> >> definitions being pulled in via "#include"  (maybe by stopping gcc after
> >> the preprocessing with -E ).
> >
> > Thanks for the hint. As far as I can see, this change is new in kernel
> > 2.6.32-rc1. In 2.6.31, which is where Pawel reported the issue, we
> > still have IR_KEYTAB_TYPE.
> >
> > Pawel, are you by any chance mixing kernel drivers of different
> > sources?
> 
> everything is under control. i've two separated builds:
> - 2.6.31 from git with debugging patch.
> - vendor kernel from rpms.
> both kernels have separated initrd images for easy booting/testing.

And both have the problem you reported?

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