linux-kernel - Re: [PATCH 2/2] i2c: busses with dynamic ids should start after fixed ids for DT

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]

Message-ID: <20150318124653.GC3580@katana>
Date:	Wed, 18 Mar 2015 13:46:53 +0100
From:	Wolfram Sang <wsa@...-dreams.de>
To:	linux-i2c@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	Bob Feretich <bob.feretich@...research.com>,
	Jean Delvare <jdelvare@...e.de>, devicetree@...r.kernel.org
Subject: Re: [PATCH 2/2] i2c: busses with dynamic ids should start after
 fixed ids for DT

On Thu, Mar 12, 2015 at 05:17:59PM +0100, Wolfram Sang wrote:
> Make sure dynamic ids do not interfere with fixed ones and let them
> start after the highest fixed id. This patch might cause different
> bus-numbers for dynamic ids, however it fixes a bug. Assume:
> 
> - fixed id0 defers probe
> - fixed id1 succeeds and registers a muxed bus with dynamic id
> - muxed bus gets id0
> - fixed id0 wants to probe again, but its fixed id is gone now
> - fixed id0 probe fails
> 
> With this patch, the fixed ids are always reserved in the DT case.
> For legacy board init, we already have a mechanism like this in
> i2c_register_board_info().
> 
> Reported-by: Bob Feretich <bob.feretich@...research.com>
> Signed-off-by: Wolfram Sang <wsa@...-dreams.de>

Fixed the checkpatch warning and applied to for-next, thanks!


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