From: Greg KH <gregkh@linuxfoundation.org>
To: Matt Corallo <yalbrymrb@mattcorallo.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-hwmon@vger.kernel.org,
Linux I2C <linux-i2c@vger.kernel.org>,
security@kernel.org
Subject: Re: PMBus memory overflow
Date: Sun, 8 Jun 2025 09:14:29 +0200 [thread overview]
Message-ID: <2025060848-reset-recovery-f67a@gregkh> (raw)
In-Reply-To: <695ebdae-7292-4a83-8aff-763da184921e@mattcorallo.com>
On Sat, Jun 07, 2025 at 09:25:44AM -0400, Matt Corallo wrote:
>
>
> On 6/7/25 4:19 AM, Greg KH wrote:
> > On Fri, Jun 06, 2025 at 04:57:37PM -0400, Matt Corallo wrote:
> > > Adding security@kernel.org cause probably they should make sure this gets fixed.
> >
> > That's not how security@k.o works, sorry. As this is already public, no
> > need for security@k.o to get involved at all, the normal development
> > process happens here now.
> >
> > So, submit a patch and people will be glad to review it!
>
> Thanks, figured I'd ask. Sadly there is a patch that folks seem to be okay
> with to fix a buffer overflow but its just sitting.
Have a pointer to that patch on lore for the maintainers involved to
review? Note, we are in the middle of the merge window, so no new
changes can be added to our trees until -rc1 is out.
thanks,
greg k-h
next prev parent reply other threads:[~2025-06-08 7:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 15:39 PMBus memory overflow Matt Corallo
2025-04-17 18:00 ` Guenter Roeck
2025-04-17 18:14 ` Matt Corallo
2025-04-18 1:21 ` Guenter Roeck
2025-04-18 21:03 ` Matt Corallo
2025-04-18 22:30 ` Guenter Roeck
2025-04-19 17:53 ` Matt Corallo
2025-04-19 19:05 ` Guenter Roeck
2025-04-19 19:29 ` Matt Corallo
2025-04-19 22:38 ` Guenter Roeck
2025-04-19 22:49 ` Guenter Roeck
2025-04-20 2:29 ` Matt Corallo
2025-04-20 3:03 ` Guenter Roeck
2025-04-25 8:16 ` Wolfram Sang
2025-05-05 20:41 ` Matt Corallo
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 [this message]
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=2025060848-reset-recovery-f67a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=security@kernel.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=yalbrymrb@mattcorallo.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