linux-kernel - Re: [PATCH] Revert "i2c: dev: switch from 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 for Android: free password hash cracker in your pocket

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

Date:	Sat, 28 May 2016 18:04:58 +0200
From:	Wolfram Sang <wsa@...-dreams.de>
To:	Dan Carpenter <dan.carpenter@...cle.com>
Cc:	linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org,
	Erico Nunes <erico.nunes@...acom.ind.br>,
	kernel-janitors@...r.kernel.org, LKP <lkp@...org>
Subject: Re: [PATCH] Revert "i2c: dev: switch from register_chrdev to cdev
 API"

> These kinds of use after frees don't always cause a runtime problem.  I
> found it using static analysis, but I bet you could detect it if you
> enabled kasan.  The other option is to enable PAGE_POISONING?

Thanks, PAGE_POISONING did trigger the issue. So, I now picked up your
patch instead of the revert because I could verify the problem and the
proper solution. Thanks again.

What I still wonder: Which analysis reported the problem to you? I
always run sparse, smatch, cppcheck, and coccicheck on the patches when
applying and no-one reported the issue.

   Wolfram

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