From: Ian Kent <raven@themaw.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
autofs mailing list <autofs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH v2 0/5] autofs updates
Date: Fri, 23 Nov 2018 18:41:41 +0800 [thread overview]
Message-ID: <154296962626.9889.644199825100770992.stgit@pluto-themaw-net> (raw)
- improve file system verification for ioctl case.
- fix potential inode leak in mount code.
- add "strictexpire" autofs mount option.
v2 changes:
- fix compile error.
- deffer some of the mount option re-factoring to try and
avoid any conflicts with linux-next.
---
Ian Kent (5):
autofs - improve ioctl sbi checks
autofs - fix possible inode leak in autofs_fill_super()
autofs - simplify parse_options() function call
autofs - change catatonic setting to a bit flag
autofs - add strictexpire mount option
fs/autofs/autofs_i.h | 11 ++++--
fs/autofs/dev-ioctl.c | 29 +++++-----------
fs/autofs/init.c | 2 +
fs/autofs/inode.c | 75 +++++++++++++++++++++++++-----------------
fs/autofs/root.c | 16 ++++++---
fs/autofs/waitq.c | 10 +++---
include/uapi/linux/auto_fs.h | 2 +
7 files changed, 78 insertions(+), 67 deletions(-)
--
Ian
next reply other threads:[~2018-11-23 21:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 10:41 Ian Kent [this message]
2018-11-23 10:41 ` [PATCH v2 1/5] autofs - improve ioctl sbi checks Ian Kent
2018-11-23 23:29 ` Andrew Morton
2018-11-25 22:57 ` Ian Kent
2018-11-23 10:41 ` [PATCH v2 2/5] autofs - fix possible inode leak in autofs_fill_super() Ian Kent
2018-11-23 10:42 ` [PATCH v2 3/5] autofs - simplify parse_options() function call Ian Kent
2018-11-23 10:42 ` [PATCH v2 4/5] autofs - change catatonic setting to a bit flag Ian Kent
2018-11-23 10:42 ` [PATCH v2 5/5] autofs - add strictexpire mount option 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=154296962626.9889.644199825100770992.stgit@pluto-themaw-net \
--to=raven@themaw.net \
--cc=akpm@linux-foundation.org \
--cc=autofs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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).