netdev - Re: [PATCH net 0/3] Add I2C bus lock for Wangxun

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: <cacbd4a1-1e7f-4067-95ad-215dde7eedcc@linux.intel.com>
Date: Fri, 23 Aug 2024 14:04:46 +0300
From: Jarkko Nikula <jarkko.nikula@...ux.intel.com>
To: Jiawen Wu <jiawenwu@...stnetic.com>, andi.shyti@...nel.org,
 andriy.shevchenko@...ux.intel.com, mika.westerberg@...ux.intel.com,
 jsd@...ihalf.com, davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
 pabeni@...hat.com, rmk+kernel@...linux.org.uk, piotr.raczynski@...el.com,
 andrew@...n.ch, linux-i2c@...r.kernel.org, netdev@...r.kernel.org
Cc: mengyuanlou@...-swift.com, duanqiangwen@...-swift.com
Subject: Re: [PATCH net 0/3] Add I2C bus lock for Wangxun

Hi
Hi

On 8/23/24 6:02 AM, Jiawen Wu wrote:
> Sometimes the driver can not get the SFP information because the I2C bus
> is accessed by the firmware at the same time. So we need to add the lock
> on the I2C bus access. The hardware semaphores perform this lock.
> 
> Jiawen Wu (3):
>    net: txgbe: add IO address in I2C platform device data
>    i2c: designware: add device private data passing to lock functions
>    i2c: designware: support hardware lock for Wangxun 10Gb NIC
> 
I was wondering the Fixes tag use in the series. Obviously patchset is 
not fixing a regression so question is what happens when issue occurs?

I don't think e.g. failing I2C transfer with an error code yet qualifies 
backporting into Linux stable?