From: Takashi Iwai <tiwai@suse.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: alsa-devel@alsa-project.org, stefanr@s5r6.in-berlin.de,
linux1394-devel@lists.sourceforge.net,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] firewire: cdev: fix potential leak of kernel stack due to uninitialized value
Date: Tue, 14 Jun 2022 15:07:46 +0200 [thread overview]
Message-ID: <87o7yvpf4t.wl-tiwai@suse.de> (raw)
In-Reply-To: <Yqh/bDB+Bvwcjjrh@workstation>
On Tue, 14 Jun 2022 14:30:36 +0200,
Takashi Sakamoto wrote:
>
> Hi Iwai-san,
>
> I have a moderate request to you for the patch which fixes an issue
> included in v5.19-rc1. If it's applicable and I can borrow your help
> again, I'd like you to send the patch to mainline via your tree.
Do you have the lore URL I can get a patch from?
> If possible, it's preferable to apply additional three patches I
> respined[1], but it could be optional since not so critical.
>
> [1] https://lore.kernel.org/alsa-devel/20220512111756.103008-1-o-takashi@sakamocchi.jp/
I can merge those, but now looking at the patches, I'm afraid that the
patch 2 ("firewire: use struct_size over open coded arithmetic") is
wrong; struct_size() takes the number of elements, and the element
type is u32, hence you're allocating 4 times large data with that
patch.
thanks,
Takashi
next prev parent reply other threads:[~2022-06-14 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 11:20 [PATCH] firewire: cdev: fix potential leak of kernel stack due to uninitialized value Takashi Sakamoto
2022-06-14 12:30 ` Takashi Sakamoto
2022-06-14 13:07 ` Takashi Iwai [this message]
2022-06-15 1:27 ` Takashi Sakamoto
2022-06-17 8:44 ` Takashi Iwai
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=87o7yvpf4t.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=dan.carpenter@oracle.com \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=o-takashi@sakamocchi.jp \
--cc=stefanr@s5r6.in-berlin.de \
/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