From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] vfs_mkobj() and mqueue-related stuff
Date: Tue, 30 Jan 2018 19:42:45 +0000 [thread overview]
Message-ID: <20180130194245.GC29051@ZenIV.linux.org.uk> (raw)
mqueue and bpf go through rather painful and similar contortions to
create objects in their dentry trees. Provide a primitive for doing that
without abusing ->mknod(), switch bpf and mqueue to it.
Another mqueue-related thing that has ended up in that branch is
on-demand creation of internal mount (based upon the work of Giuseppe Scrivano).
The following changes since commit ae64f9bd1d3621b5e60d7363bc20afb46aede215:
Linux 4.15-rc2 (2017-12-03 11:01:47 -0500)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.mqueue
for you to fetch changes up to 36735a6a2b5e042db1af956ce4bcc13f3ff99e21:
mqueue: switch to on-demand creation of internal mount (2018-01-05 11:54:37 -0500)
----------------------------------------------------------------
Al Viro (9):
new primitive: vfs_mkobj()
bpf_obj_do_pin(): switch to vfs_mkobj(), quit abusing ->mknod()
mqueue: switch to vfs_mkobj(), quit abusing ->d_fsdata
move dentry_open() calls up into do_mq_open()
mqueue: fold mq_attr_ok() into mqueue_get_inode()
do_mq_open(): move all work prior to dentry_open() into a helper
mqueue: clean prepare_open() up
tidy do_mq_open() up a bit
mqueue: switch to on-demand creation of internal mount
fs/namei.c | 21 +++++
include/linux/fs.h | 4 +
ipc/mqueue.c | 241 ++++++++++++++++++++++++-----------------------------
kernel/bpf/inode.c | 50 +++++------
4 files changed, 158 insertions(+), 158 deletions(-)
reply other threads:[~2018-01-30 19:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180130194245.GC29051@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).