linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Edward AD <eadavis@sina.com>
Cc: syzbot+b5d1f455d385b2c7da3c@syzkaller.appspotmail.com,
	jirislaby@kernel.org, linux-kernel@vger.kernel.org,
	linux-serial@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] tty: fix memory leak in gsm_activate_mux
Date: Mon, 18 Sep 2023 10:06:58 +0200	[thread overview]
Message-ID: <2023091826-spherical-shindig-016b@gregkh> (raw)
In-Reply-To: <20230915112324.941574-1-eadavis@sina.com>

On Fri, Sep 15, 2023 at 07:23:24PM +0800, Edward AD wrote:
> When the call to gsm_register_devices() fails, we need to reclaim the memory
> requested in gsm_dlci_alloc().
> 
> Fixes: 01aecd917114 ("tty: n_gsm: fix tty registration before control channel open")
> Reported-and-tested-by: syzbot+b5d1f455d385b2c7da3c@syzkaller.appspotmail.com
> Signed-off-by: Edward AD <eadavis@sina.com>
> ---
>  drivers/tty/n_gsm.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)

This message never made it to lore.kernel.org, so you might need to fix
up your email system so that it doesn't get dropped from there.

Can you do so and resend?

thanks,

greg k-h

  parent reply	other threads:[~2023-09-18  8:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15  6:29 [syzbot] [serial?] memory leak in gsm_activate_mux syzbot
     [not found] ` <20230915112324.941574-1-eadavis@sina.com>
2023-09-18  8:06   ` Greg KH [this message]
     [not found]     ` <20230918084526.2824669-1-eadavis@sina.com>
2023-09-18  9:13       ` [PATCH] tty: fix " Greg KH
     [not found]         ` <20230918104836.2933871-1-eadavis@sina.com>
2023-09-18 12:02           ` Greg KH
     [not found]             ` <20230919034524.3425915-2-eadavis@sina.com>
2023-09-19  7:35               ` Greg KH
2023-09-19  8:02                 ` Edward AD
2023-09-19  8:29                   ` Greg KH
2023-09-19  9:22                     ` Edward AD
2023-09-19  9:31                       ` Greg KH
2023-09-19  9:55                         ` Edward AD
2023-09-20  6:38                         ` Edward AD

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=2023091826-spherical-shindig-016b@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=eadavis@sina.com \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=syzbot+b5d1f455d385b2c7da3c@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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;
as well as URLs for NNTP newsgroup(s).