From: Ian Kent <raven@themaw.net>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Howells <dhowells@redhat.com>,
Miklos Szeredi <miklos@szeredi.hu>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/5] autofs: misc patches
Date: Fri, 08 Jul 2022 09:42:55 +0800 [thread overview]
Message-ID: <165724445154.30914.10970894936827635879.stgit@donald.themaw.net> (raw)
This series contains several patches that resulted mostly from comments
made by Al Viro (quite a long time ago now).
They are:
- make use of the .permission() method for access checks.
- use dentry info count instead of simple_empty() to avoid
taking a spinlock.
- add a use cases comment to autofs_mountpoint_changed().
Others:
- fix usage consistency problem with dentry info count.
- remove unused inode field from info struct.
Signed-off-by: Ian Kent <raven@themaw.net>
---
Ian Kent (5):
autofs: use inode permission method for write access
autofs: make dentry info count consistent
autofs: use dentry info count instead of simple_empty()
autofs: add comment about autofs_mountpoint_changed()
autofs: remove unused ino field inode
fs/autofs/autofs_i.h | 7 ++-
fs/autofs/expire.c | 2 +-
fs/autofs/inode.c | 1 +
fs/autofs/root.c | 108 ++++++++++++++++++++-----------------------
4 files changed, 57 insertions(+), 61 deletions(-)
--
Ian
next reply other threads:[~2022-07-08 1:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 1:42 Ian Kent [this message]
2022-07-08 1:43 ` [PATCH 1/5] autofs: use inode permission method for write access Ian Kent
2022-07-08 1:43 ` [PATCH 2/5] autofs: make dentry info count consistent Ian Kent
2022-07-08 1:43 ` [PATCH 3/5] autofs: use dentry info count instead of simple_empty() Ian Kent
2022-07-08 1:43 ` [PATCH 4/5] autofs: add comment about autofs_mountpoint_changed() Ian Kent
2022-07-08 1:43 ` [PATCH 5/5] autofs: remove unused ino field inode Ian Kent
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=165724445154.30914.10970894936827635879.stgit@donald.themaw.net \
--to=raven@themaw.net \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@ZenIV.linux.org.uk \
/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.