[<prev] [next>] [day] [month] [year] [list]
Message-ID: <5524723.20003.1710468913133@app142018.ycg3.service-now.com>
Date: Thu, 14 Mar 2024 19:15:13 -0700 (PDT)
From: Red Hat Product Security <secalert@...hat.com>
To: richardcochran@...il.com, syzkaller@...glegroups.com,
liujingfeng@...nxin.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: memory leak in posix_clock_open
Hello!
INC2889741 (memory leak in posix_clock_open) has been updated.
Opened for: liujingfeng@...nxin.com
Followers: richardcochran@...il.com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, syzkaller@...glegroups.com
A Guest updated your request with the following comments:
Reply from: qiang.zhang1211@...il.com [mailto:qiang.zhang1211@...il.com]
>
> On Mon, Mar 11 2024 at 17:46, Z qiang wrote:
> >
> > diff --git a/kernel/time/posix-clock.c b/kernel/time/posix-clock.c
> > index 9de66bbbb3d1..71d9d8c394fa 100644
> > --- a/kernel/time/posix-clock.c
> > +++ b/kernel/time/posix-clock.c
> > @@ -137,6 +137,8 @@ static int posix_clock_open(struct inode *inode,
> > struct file *fp)
> >
> > if (!err) {
> > get_device(clk->dev);
> > + } else {
> > + kfree(pccontext);
> > }
> > out:
> > up_read(&clk->rwsem);
>
> Looks about right. Can you please send a proper patch?
I will send a patch.
Thanks,
Zqiang
How can I track and update my request?
To respond, reply to this email. You may also create a new email and include the request number (INC2889741) in the subject.
Thank you,
Product Security
Ref:MSG86727590
Content of type "text/html" skipped
Powered by blists - more mailing lists