[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aBBmmNlM3_zjNMC3@shikoro>
Date: Tue, 29 Apr 2025 07:41:44 +0200
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
To: Akhil R <akhilrajeev@...dia.com>
Cc: Andi Shyti <andi.shyti@...nel.org>,
Laxman Dewangan <ldewangan@...dia.com>,
"digetx@...il.com" <digetx@...il.com>,
"thierry.reding@...il.com" <thierry.reding@...il.com>,
Jon Hunter <jonathanh@...dia.com>,
"wsa@...nel.org" <wsa@...nel.org>,
"linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Thierry Reding <treding@...dia.com>
Subject: Re: [PATCH v2 RESEND] i2c: tegra: check msg length in SMBUS block
read
Hi Akhil,
> Yes. We have had issues where the client device sends '0' as length if the
Can you reveal which client that is?
> transfer is terminated abruptly at the client's side. The actual fix is in the client's
> driver, but this check here would ensure that the master does not run into
> trouble either.
Correct.
Happy hacking!
Wolfram
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists