From: Matt Corallo <yalbrymrb@mattcorallo.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Guenter Roeck <linux@roeck-us.net>,
linux-hwmon@vger.kernel.org,
Linux I2C <linux-i2c@vger.kernel.org>
Subject: Re: PMBus memory overflow
Date: Mon, 5 May 2025 16:41:09 -0400 [thread overview]
Message-ID: <3a9ab7bf-6761-4a14-983e-e6bb288ce58a@mattcorallo.com> (raw)
In-Reply-To: <aAtEydwUfVcE0XeA@shikoro>
On 4/25/25 4:16 AM, Wolfram Sang wrote:
>
>> Wolfram, what do you suggest ? Fixing the cp2112 driver is obviously necessary, but
>> I do wonder if a check such as the one above would be appropriate as well, possibly
>> even combined with a WARN_ONCE().
>
> How annoying, there was still an unchecked case left? Sorry. Yes, the
> core can have a check for a short-term solution. The long-term solution
> is to support SMBUS3.x which allows for 255 byte transfers.
Thanks!
Any update here? I guess we already have a patch so no use in me trying to write one. Would be nice
to get this in a pull so it can head through backports.
Thanks,
Matt
next prev parent reply other threads:[~2025-05-05 21:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <985cd95f-155b-4b8a-9fe7-59938d0c2b8f@mattcorallo.com>
[not found] ` <9e01e3ec-3ac5-4d83-a065-d00d568b9cc7@roeck-us.net>
[not found] ` <e030f44f-11ee-4739-b9d3-c22883bbbf02@mattcorallo.com>
[not found] ` <336f298f-497f-4dd9-97ee-50b81221be06@roeck-us.net>
[not found] ` <1b1eccff-a306-4e17-a6bf-fd3203c61605@mattcorallo.com>
[not found] ` <1edc8396-535d-4cdf-bbb7-11d559d4c257@roeck-us.net>
[not found] ` <cfc2b3c8-3f94-407a-a4d5-e7d81686eb2d@mattcorallo.com>
[not found] ` <84258b48-03b5-4129-bed5-f8200996f2eb@roeck-us.net>
[not found] ` <fcfd78d2-238d-4b68-b6ec-5ee809c4ef08@mattcorallo.com>
[not found] ` <eb5796e8-de76-4e91-9192-65b9af7a4d49@roeck-us.net>
[not found] ` <284466fd-39e8-419e-8af5-41dbabb788af@roeck-us.net>
[not found] ` <d5abeb59-8286-425c-9f78-cd60b0e26ada@mattcorallo.com>
2025-04-20 3:03 ` PMBus memory overflow Guenter Roeck
2025-04-25 8:16 ` Wolfram Sang
2025-05-05 20:41 ` Matt Corallo [this message]
2025-05-05 20:50 ` Guenter Roeck
2025-05-05 20:57 ` Matt Corallo
2025-05-06 1:39 ` Guenter Roeck
2025-06-06 20:57 ` Matt Corallo
2025-06-07 8:19 ` Greg KH
2025-06-07 13:25 ` Matt Corallo
2025-06-08 7:14 ` Greg KH
2025-06-09 13:57 ` Matt Corallo
2026-03-01 13:46 ` Matt Corallo
2026-03-01 16:12 ` Kees Cook
2026-03-01 17:10 ` Matt Corallo
2026-03-01 20:17 ` Guenter Roeck
2026-03-02 5:09 ` Kees Cook
2026-03-02 5:19 ` Guenter Roeck
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=3a9ab7bf-6761-4a14-983e-e6bb288ce58a@mattcorallo.com \
--to=yalbrymrb@mattcorallo.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wsa+renesas@sang-engineering.com \
/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