From: Kees Cook <keescook@chromium.org>
To: Kalesh Singh <kaleshsingh@google.com>
Cc: jannh@google.com, jeffv@google.com, surenb@google.com,
minchan@kernel.org, hridya@google.com, rdunlap@infradead.org,
christian.koenig@amd.com, willy@infradead.org,
viro@zeniv.linux.org.uk, kernel-team@android.com,
Alexey Dobriyan <adobriyan@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Alexey Gladkov <gladkov.alexey@gmail.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Christian Brauner <christian.brauner@ubuntu.com>,
Michel Lespinasse <walken@google.com>,
Bernd Edlinger <bernd.edlinger@hotmail.de>,
Andrei Vagin <avagin@gmail.com>, Helge Deller <deller@gmx.de>,
James Morris <jamorris@linux.microsoft.com>,
Serge Hallyn <serge@hallyn.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [RESEND PATCH v6 2/2] procfs/dmabuf: Add inode number to /proc/*/fdinfo
Date: Wed, 17 Mar 2021 22:54:34 -0700 [thread overview]
Message-ID: <202103172254.478DE154@keescook> (raw)
In-Reply-To: <20210308170651.919148-2-kaleshsingh@google.com>
On Mon, Mar 08, 2021 at 05:06:41PM +0000, Kalesh Singh wrote:
> And 'ino' field to /proc/<pid>/fdinfo/<FD> and
> /proc/<pid>/task/<tid>/fdinfo/<FD>.
>
> The inode numbers can be used to uniquely identify DMA buffers
> in user space and avoids a dependency on /proc/<pid>/fd/* when
> accounting per-process DMA buffer sizes.
>
> Signed-off-by: Kalesh Singh <kaleshsingh@google.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
--
Kees Cook
next prev parent reply other threads:[~2021-03-18 5:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 17:06 [RESEND PATCH v6 1/2] procfs: Allow reading fdinfo with PTRACE_MODE_READ Kalesh Singh
2021-03-08 17:06 ` [RESEND PATCH v6 2/2] procfs/dmabuf: Add inode number to /proc/*/fdinfo Kalesh Singh
2021-03-18 5:54 ` Kees Cook [this message]
2021-03-08 17:54 ` [RESEND PATCH v6 1/2] procfs: Allow reading fdinfo with PTRACE_MODE_READ Christian König
2021-03-08 18:06 ` Kalesh Singh
2021-03-18 5:55 ` Kees Cook
2021-03-18 6:14 ` Kalesh Singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202103172254.478DE154@keescook \
--to=keescook@chromium.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=avagin@gmail.com \
--cc=bernd.edlinger@hotmail.de \
--cc=christian.brauner@ubuntu.com \
--cc=christian.koenig@amd.com \
--cc=corbet@lwn.net \
--cc=deller@gmx.de \
--cc=ebiederm@xmission.com \
--cc=gladkov.alexey@gmail.com \
--cc=hridya@google.com \
--cc=jamorris@linux.microsoft.com \
--cc=jannh@google.com \
--cc=jeffv@google.com \
--cc=kaleshsingh@google.com \
--cc=kernel-team@android.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=rdunlap@infradead.org \
--cc=serge@hallyn.com \
--cc=surenb@google.com \
--cc=viro@zeniv.linux.org.uk \
--cc=walken@google.com \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.