From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Akhil R <akhilrajeev@nvidia.com>
Cc: Andi Shyti <andi.shyti@kernel.org>,
Laxman Dewangan <ldewangan@nvidia.com>,
"digetx@gmail.com" <digetx@gmail.com>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
Jon Hunter <jonathanh@nvidia.com>,
"wsa@kernel.org" <wsa@kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thierry Reding <treding@nvidia.com>
Subject: Re: [PATCH v2 RESEND] i2c: tegra: check msg length in SMBUS block read
Date: Tue, 29 Apr 2025 07:41:44 +0200 [thread overview]
Message-ID: <aBBmmNlM3_zjNMC3@shikoro> (raw)
In-Reply-To: <PH7PR12MB8178416B09D217B77CC43C04C0802@PH7PR12MB8178.namprd12.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 351 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-04-29 5:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 5:33 [PATCH v2 RESEND] i2c: tegra: check msg length in SMBUS block read Akhil R
2025-04-28 23:34 ` Andi Shyti
2025-04-29 3:17 ` Wolfram Sang
2025-04-29 4:37 ` Akhil R
2025-04-29 5:41 ` Wolfram Sang [this message]
2025-04-29 9:51 ` Akhil R
2025-04-29 11:29 ` Andi Shyti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aBBmmNlM3_zjNMC3@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=akhilrajeev@nvidia.com \
--cc=andi.shyti@kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=treding@nvidia.com \
--cc=wsa@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox