Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.35 as permitted sender) client-ip=23.128.96.35;
From:   Edward AD <twuufnxlz@gmail.com>
To:     gregkh@linuxfoundation.org
Cc:     eadavis@sina.com, jirislaby@kernel.org,
        linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
        syzbot+b5d1f455d385b2c7da3c@syzkaller.appspotmail.com,
        syzkaller-bugs@googlegroups.com, twuufnxlz@gmail.com
Subject: Re: [PATCH] tty: fix memory leak in gsm_activate_mux
Date:   Tue, 19 Sep 2023 17:22:26 +0800
Message-ID: <20230919092225.3732786-2-twuufnxlz@gmail.com>
In-Reply-To: <2023091922-unplug-flask-f2e5@gregkh>
References: <2023091922-unplug-flask-f2e5@gregkh>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Tue, 19 Sep 2023 10:29:08 +0200 Greg KH 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 <twuufnxlz@gmail.com>
> 
> Please use your company name/email address, and then just set a manual
> "From:" line as the first line in the changelog as the documentation
> asks.  That's how developers work around their broken corporate email
> systems (but really, you should go and poke your IT group to fix it.)
This repair was completed in my personal time. Additionally, there may be a 
possibility of the company's email being thrown away by 'lore.kernel.org'. 
If you are not very strict with this, I will continue to use my private email.

I will only keep one line starting with 'From:' in the patch.

Thanks,
edward