[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YoC0yg5FWDxJocV5@kroah.com>
Date: Sun, 15 May 2022 10:07:38 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Shreenidhi Shedi <yesshedi@...il.com>
Cc: arnd@...db.de, linux-kernel@...r.kernel.org,
Shreenidhi Shedi <sshedi@...are.com>
Subject: Re: [PATCH 1/3] char: lp: ensure that index has not exceeded LP_NO
On Sun, May 15, 2022 at 01:24:53PM +0530, Shreenidhi Shedi wrote:
> After finishing the loop, index value can be equal to LP_NO and lp_table
> array is of size LP_NO, so this can end up in accessing an out of bound
> address in lp_register function.
>
> Signed-off-by: Shreenidhi Shedi <sshedi@...are.com>
> ---
> drivers/char/lp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/char/lp.c b/drivers/char/lp.c
> index bd95aba1f..e61060f3c 100644
> --- a/drivers/char/lp.c
> +++ b/drivers/char/lp.c
> @@ -971,7 +971,7 @@ static void lp_attach(struct parport *port)
> if (port_num[i] == -1)
> break;
>
> - if (!lp_register(i, port))
> + if (i < LP_NO && !lp_register(i, port))
> lp_count++;
> break;
>
> --
> 2.36.1
>
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:
- This looks like a new version of a previously submitted patch, but you
did not list below the --- line any changes from the previous version.
Please read the section entitled "The canonical patch format" in the
kernel file, Documentation/SubmittingPatches for what needs to be done
here to properly describe 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