[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0c6fcfb1-a528-4e05-9fe3-f1671784569e@stanley.mountain>
Date: Mon, 2 Dec 2024 18:43:41 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Benoît Sevens <bsevens@...gle.com>
Cc: Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
wangdicheng <wangdicheng@...inos.cn>,
Manuel Barrio Linares <mbarriolinares@...il.com>,
Lianqin Hu <hulianqin@...o.com>,
Shen Lichuan <shenlichuan@...o.com>, Cyan Nyan <cyan.vtb@...il.com>,
linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] ALSA: usb-audio: Fix a DMA to stack memory bug
On Mon, Dec 02, 2024 at 04:05:01PM +0100, Benoît Sevens wrote:
> Hi Dan,
>
> On Mon, 2 Dec 2024 at 13:57, Dan Carpenter <dan.carpenter@...aro.org> wrote:
> >
> > The usb_get_descriptor() function does DMA so we're not allowed
> > to use a stack buffer for that. Doing DMA to the stack is not portable
> > all architectures. Move the "new_device_descriptor" from being stored
> > on the stack and allocate it with kmalloc() instead.
> >
>
> Thanks for fixing this. It looks good to me.
>
> Note that the commit that is being fixed is already queued for
> backporting, so I don't know how this usually goes then.
>
It's fine. The stable scripts look for fixes to stable patches.
But I also CC'd stable because your commit is CC'd for stable. Even CC'ing
stable shouldn't be necessary here, maybe there is a rebase or something so the
Fixes tag gets broken or maybe something else goes wrong. CC'ing stable is just
an extra way to be careful.
regards,
dan carpenter
Powered by blists - more mailing lists