lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Fri, 14 Jun 2019 15:04:42 +0530
From:   Sumit Semwal <>
To:     Chenbo Feng <>
Cc:     LKML <>,
        DRI mailing list <>,
        Android Kernel Team <>
Subject: Re: [PATCH v5 0/3] Improve the dma-buf tracking

Hi Chenbo,

On Fri, 14 Jun 2019 at 04:04, Chenbo Feng <> wrote:
> Currently, all dma-bufs share the same anonymous inode. While we can count
> how many dma-buf fds or mappings a process has, we can't get the size of
> the backing buffers or tell if two entries point to the same dma-buf. And
> in debugfs, we can get a per-buffer breakdown of size and reference count,
> but can't tell which processes are actually holding the references to each
> buffer.

Thanks for the series; applied to drm-misc-next.


Powered by blists - more mailing lists