All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ajay Garg <ajaygargnsit@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tty: vt: keyboard: Free dynamic-memory only if kmalloc'ed.
Date: Sat, 6 Nov 2021 16:13:48 +0530	[thread overview]
Message-ID: <CAHP4M8XW3NBvR7XFv6TogCd_eR=wMTyTQs0HToFk0p4Oj6NkQQ@mail.gmail.com> (raw)
In-Reply-To: <YYZN30qfaKMskVwE@kroah.com>

Thanks, will ensure that I run scripts/checkpatch.pl before posting
any patch from now on.

The v2 patch is posted at :
https://lore.kernel.org/linux-serial/20211106104053.98761-1-ajaygargnsit@gmail.com/T/#u

On Sat, Nov 6, 2021 at 3:11 PM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Sat, Nov 06, 2021 at 03:02:02PM +0530, Ajay Garg wrote:
> > In "vt_do_kdgkb_ioctl", kbs is kmalloced, if cmd is one of
> > KDGKBSENT or KDGSKBSENT.
> >
> > If cmd is none of the above, no kbs is kmalloced, and thus,
> > kbs must only be kfreed if it is really kmalloced.
> >
> > Signed-off-by: Ajay Garg <ajaygargnsit@gmail.com>
> > ---
> >  drivers/tty/vt/keyboard.c | 5 +++--
> >  1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/tty/vt/keyboard.c b/drivers/tty/vt/keyboard.c
> > index dfef7de8a057..95839987c79c 100644
> > --- a/drivers/tty/vt/keyboard.c
> > +++ b/drivers/tty/vt/keyboard.c
> > @@ -2049,7 +2049,7 @@ int vt_do_kdgkb_ioctl(int cmd, struct kbsentry __user *user_kdgkb, int perm)
> >  {
> >       unsigned char kb_func;
> >       unsigned long flags;
> > -     char *kbs;
> > +     char *kbs = NULL;
> >       int ret;
> >
> >       if (get_user(kb_func, &user_kdgkb->kb_func))
> > @@ -2092,7 +2092,8 @@ int vt_do_kdgkb_ioctl(int cmd, struct kbsentry __user *user_kdgkb, int perm)
> >               break;
> >       }
> >
> > -     kfree(kbs);
> > +        if(kbs)
> > +            kfree(kbs);
> >
> >       return ret;
> >  }
> > --
> > 2.30.2
> >
>
>
> 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:
>
> - Your patch contains warnings and/or errors noticed by the
>   scripts/checkpatch.pl tool.
>
> 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

      reply	other threads:[~2021-11-06 10:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-06  9:32 [PATCH] tty: vt: keyboard: Free dynamic-memory only if kmalloc'ed Ajay Garg
2021-11-06  9:41 ` Greg KH
2021-11-06 10:43   ` Ajay Garg [this message]

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='CAHP4M8XW3NBvR7XFv6TogCd_eR=wMTyTQs0HToFk0p4Oj6NkQQ@mail.gmail.com' \
    --to=ajaygargnsit@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.