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: <eepxdvnjgynjtavq2epiz2gb7ztibnluyegvlcxhpk27mosi6e@gkocjynuxoyz>
Date: Thu, 27 Feb 2025 19:54:50 +0100
From: Andi Shyti <andi.shyti@...nel.org>
To: Anindya Sundar Gayen <anindya.sg@...sung.com>
Cc: linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org, 
	aswani.reddy@...sung.com, pankaj.dubey@...sung.com
Subject: Re: [PATCH] i2c-algo-bit: Added the bus lock during a i2c transaction

Hi,

On Tue, Feb 25, 2025 at 05:03:14PM +0530, Anindya Sundar Gayen wrote:
> Earlier i2c-bus lock was not available to i2c-algo-bit driver
> for that reason if there are back to back i2c transaction occurs
> it may be possible to occur a race condition.
> 
> To avoid the race condition we added a mutex lock mechanism which will
> help to protect the i2c_outb()with a proper lock.

what is the issue you are trying to fix? Can you refer to a
practical failure you received?

Thanks,
Andi

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ