[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2024020709-familiar-slapping-a96a@gregkh>
Date: Wed, 7 Feb 2024 10:16:20 +0000
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Fedor Pchelkin <pchelkin@...ras.ru>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
Jeffrey Hugo <quic_jhugo@...cinc.com>,
Kalle Valo <quic_kvalo@...cinc.com>,
Carl Vanderlip <quic_carlv@...cinc.com>,
Sujeev Dias <sdias@...eaurora.org>,
Siddartha Mohanadoss <smohanad@...eaurora.org>, mhi@...ts.linux.dev,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
Alexey Khoroshilov <khoroshilov@...ras.ru>,
lvc-project@...uxtesting.org
Subject: Re: [PATCH] bus: mhi: host: free buffer on error in
mhi_alloc_bhie_table
On Wed, Feb 07, 2024 at 09:51:36AM +0300, Fedor Pchelkin wrote:
> img_info->mhi_buf should be freed on error path in mhi_alloc_bhie_table().
> This error case is rare but still needs to be fixed.
>
> Found by Linux Verification Center (linuxtesting.org).
>
> Fixes: 3000f85b8f47 ("bus: mhi: core: Add support for basic PM operations")
> Signed-off-by: Fedor Pchelkin <pchelkin@...ras.ru>
> ---
> drivers/bus/mhi/host/boot.c | 1 +
> 1 file changed, 1 insertion(+)
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- You have marked a patch with a "Fixes:" tag for a commit that is in an
older released kernel, yet you do not have a cc: stable line in the
signed-off-by area at all, which means that the patch will not be
applied to any older kernel releases. To properly fix this, please
follow the documented rules in the
Documentation/process/stable-kernel-rules.rst file for how to resolve
this.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
Powered by blists - more mailing lists