From: Kumar Kartikeya Dwivedi <memxor@gmail.com>
To: io-uring@vger.kernel.org
Cc: Pavel Emelyanov <xemul@openvz.org>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jens Axboe <axboe@kernel.dk>,
Pavel Begunkov <asml.silence@gmail.com>,
Daniel Colascione <dancol@google.com>,
Paul Moore <paul@paul-moore.com>,
Eric Biggers <ebiggers@google.com>,
Lokesh Gidra <lokeshgidra@google.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Create io_uring fd with ephemeral inode
Date: Wed, 19 May 2021 17:00:55 +0530 [thread overview]
Message-ID: <20210519113058.1979817-1-memxor@gmail.com> (raw)
This set converts io_uring to use secure anon_inodes (with a newly allocated
non-S_PRIVATE inode) for each individual instance. In addition to allowing LSM
modules to enforce policy using the inode context, it also enables
checkpoint/restore usecases by allowing mapping the VMA to the open fd in a
task. Offset is already available to determine rings mapped per region, so this
was the only missing piece in establishing region <-> io_uring instance mapping.
LSM tie up has been left out of this set for now.
Kumar Kartikeya Dwivedi (2):
fs: anon_inodes: export anon_inode_getfile_secure helper
fs: io_uring: convert to use anon_inode_getfile_secure
fs/anon_inodes.c | 9 +++++++++
fs/io_uring.c | 4 ++--
include/linux/anon_inodes.h | 4 ++++
3 files changed, 15 insertions(+), 2 deletions(-)
--
2.31.1
next reply other threads:[~2021-05-19 11:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 11:30 Kumar Kartikeya Dwivedi [this message]
2021-05-19 11:30 ` [PATCH 1/2] fs: anon_inodes: export anon_inode_getfile_secure helper Kumar Kartikeya Dwivedi
2021-05-19 15:22 ` Paul Moore
2021-05-19 23:07 ` Kumar Kartikeya Dwivedi
2021-05-20 2:29 ` Paul Moore
2021-05-19 16:04 ` Christoph Hellwig
2021-05-19 11:30 ` [PATCH 2/2] fs: io_uring: convert to use anon_inode_getfile_secure Kumar Kartikeya Dwivedi
2021-05-19 15:18 ` [PATCH 0/2] Create io_uring fd with ephemeral inode Paul Moore
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=20210519113058.1979817-1-memxor@gmail.com \
--to=memxor@gmail.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=dancol@google.com \
--cc=ebiggers@google.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lokeshgidra@google.com \
--cc=paul@paul-moore.com \
--cc=viro@zeniv.linux.org.uk \
--cc=xemul@openvz.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).