[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y00beLWxbp1ODaB/@kroah.com>
Date: Mon, 17 Oct 2022 11:08:08 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Yang Yingliang <yangyingliang@...wei.com>
Cc: linux-kernel@...r.kernel.org, rafael@...nel.org
Subject: Re: [PATCH] kobject: fix possible memory leak in
kset_create_and_add()
On Mon, Oct 17, 2022 at 05:01:04PM +0800, Yang Yingliang wrote:
>
> On 2022/10/17 16:49, Greg KH wrote:
> > On Mon, Oct 17, 2022 at 04:13:03PM +0800, Yang Yingliang wrote:
> > > Hi,
> > >
> > > On 2022/10/17 12:51, Greg KH wrote:
> > > > On Mon, Oct 17, 2022 at 10:33:27AM +0800, Yang Yingliang wrote:
> > > > > If kset_register() fails in kset_create_and_add(), the name allocated
> > > > > in kset_create() will be leaked.
> > > > How is kset_create_and_add() failing? Is this in a real kernel, or
> > > > created with a fake fault injection?
> > > Inject fault while probing module qemu_fw_cfg, kset_create_and_add() may
> > > fail.
> > Ah good, it's never being hit in a real situation. The next time you
> > submit patches that are found like this, please include this type of
> > information.
> OK. Do I need to send a v2 with commit message update.
That would be wonderful for you to do, thank you!
Also do the same thing for the other patches you sent that fix up error
paths like this.
thanks,
greg k-h
Powered by blists - more mailing lists