[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpU7kXXGuxeOVvAGLoBRvjrhpuw2D=ih=PagGXKK-g_muw@mail.gmail.com>
Date: Thu, 27 Feb 2020 13:38:03 -0800
From: Cong Wang <xiyou.wangcong@...il.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-media@...r.kernel.org, dri-devel@...ts.freedesktop.org,
LKML <linux-kernel@...r.kernel.org>,
linaro-mm-sig@...ts.linaro.org,
syzbot+b2098bc44728a4efb3e9@...kaller.appspotmail.com,
Chenbo Feng <fengc@...gle.com>,
Sumit Semwal <sumit.semwal@...aro.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] dma-buf: free dmabuf->name in dma_buf_release()
On Tue, Feb 25, 2020 at 5:54 PM Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> On Tue, 25 Feb 2020 12:44:46 -0800 Cong Wang <xiyou.wangcong@...il.com> wrote:
>
> > dma-buff name can be set via DMA_BUF_SET_NAME ioctl, but once set
> > it never gets freed.
> >
> > Free it in dma_buf_release().
> >
> > ...
> >
> > --- a/drivers/dma-buf/dma-buf.c
> > +++ b/drivers/dma-buf/dma-buf.c
> > @@ -108,6 +108,7 @@ static int dma_buf_release(struct inode *inode, struct file *file)
> > dma_resv_fini(dmabuf->resv);
> >
> > module_put(dmabuf->owner);
> > + kfree(dmabuf->name);
> > kfree(dmabuf);
> > return 0;
> > }
>
> ow. Is that ioctl privileged?
It looks unprivileged to me, as I don't see capable() called along
the path.
Thanks.
Powered by blists - more mailing lists