linux-kernel - Re: next-20160314 - crash in i2c_dev_init/bus_register

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:	Thu, 17 Mar 2016 21:52:25 +0100
From:	Wolfram Sang <wsa@...-dreams.de>
To:	Valdis Kletnieks <Valdis.Kletnieks@...edu>
Cc:	linux-kernel@...r.kernel.org, linux-i2c@...r.kernel.org
Subject: Re: next-20160314 - crash in i2c_dev_init/bus_register_notifier at
 boot

On Thu, Mar 17, 2016 at 10:59:51AM -0400, Valdis Kletnieks wrote:
> Seeing this consistent crash on next-20160314.  Sorry for shortened traceback,
> hand-transcribed as the crash doesn't get logged to /sys/fs/pstore as
> expected. next-20160307 works just fine.
> 
> BUG: unable to handle kernel NULL pointer dereference at 000000000260
> IP: blocking_notifier_chain_register+0x37/0xd0
> ...
> Call Trace:
> bus_register_notifier+0x1c/0x20
> i2c_dev_init+0x9c/0xf2
> do_one_initcall_+0x99/0x210
> ? set_debug_rodata+0x12/0x12
> kernel_init_freeable+0x1b3/0x240
> kernel_init+0x3/0x100
> 
> 'git blame' doesn't seem to find anything relevant and recent in
> kernel/notifier.c or drivers/i2c/i2c-dev.c.  Does this ring any
> bells, or is it time to bisect?

Can you try a newer -next or apply this patch on top?

https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/patch/drivers/i2c?id=b980a26d02d1f54be31346666222304fcd27ea33

I think this should solve it.

Thanks for reporting!

   Wolfram


Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)