public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shreenidhi Shedi <yesshedi@gmail.com>
To: gregkh@linuxfoundation.org, arnd@arndb.de
Cc: yesshedi@gmail.com, Shreenidhi Shedi <sshedi@vmware.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] char: lp: ensure that index has not exceeded LP_NO
Date: Fri, 3 Jun 2022 17:27:06 +0530	[thread overview]
Message-ID: <64570db1-e9f2-4f23-1d14-3d4b35776bca@gmail.com> (raw)
In-Reply-To: <20220515075455.306082-1-sshedi@vmware.com>

On 15/05/22 1:24 pm, 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@vmware.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;
>  

Hi Greg and Arnd Bergmann,

Please review the above changes. Ignore second patch.

--
Shedi

  parent reply	other threads:[~2022-06-03 11:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-15  7:54 [PATCH 1/3] char: lp: ensure that index has not exceeded LP_NO Shreenidhi Shedi
2022-05-15  7:54 ` [PATCH 2/3] char: lp: remove redundant initialization of err Shreenidhi Shedi
2022-05-15  8:08   ` Greg KH
2022-05-15  7:54 ` [PATCH 3/3] char: lp: fix most of checkspec.pl warnings & errors Shreenidhi Shedi
2022-05-15  8:08   ` Greg KH
2022-05-15  8:07 ` [PATCH 1/3] char: lp: ensure that index has not exceeded LP_NO Greg KH
2022-06-03 11:57 ` Shreenidhi Shedi [this message]
2022-06-03 12:02   ` Shreenidhi Shedi
2022-06-03 12:44     ` Greg KH
2022-06-03 12:49       ` Shreenidhi Shedi

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=64570db1-e9f2-4f23-1d14-3d4b35776bca@gmail.com \
    --to=yesshedi@gmail.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sshedi@vmware.com \
    /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