From: Oliver Neukum <oneukum@suse.com>
To: Griffin Kroah-Hartman <griffin@kroah.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: image: mdc800: change kmalloc() to kzalloc()
Date: Tue, 1 Sep 2026 14:17:54 +0200 [thread overview]
Message-ID: <0ff47679-3f00-4cb4-b1ee-2b3a0e15b13a@suse.com> (raw)
In-Reply-To: <20260819-usb_misc_random-v1-1-43a0dcee3a32@kroah.com>
On 19.08.26 12:04, Griffin Kroah-Hartman wrote:
> Change the kmalloc() calls in usb_mdc800_init() for irq_urb_buffer and
> download_urb_buffer to kzalloc(), avoiding potential stack leaks if a
> shorter message is received in mdc800_usb_irq() and
> mdc800_usb_download_notify()
Hi,
thanks for the patch, but is this the right approach?
If we get too short a reply we shouldn't process it
at all.
Regards
Oliver
next prev parent reply other threads:[~2026-09-01 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 10:04 [PATCH] usb: image: mdc800: change kmalloc() to kzalloc() Griffin Kroah-Hartman
2026-09-01 12:17 ` Oliver Neukum [this message]
2026-09-01 14:30 ` Greg Kroah-Hartman
2026-09-02 9:35 ` Oliver Neukum
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=0ff47679-3f00-4cb4-b1ee-2b3a0e15b13a@suse.com \
--to=oneukum@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=griffin@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.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