From: Miklos Szeredi <mszeredi@redhat.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org
Subject: [PATCH 00/12] various vfs patches
Date: Thu, 28 Nov 2019 16:59:28 +0100 [thread overview]
Message-ID: <20191128155940.17530-1-mszeredi@redhat.com> (raw)
Hi Al,
This is a dump of my current vfs patch queue, all have been posted in one
form or another.
Also available as a git branch:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git#for-viro
Please apply.
Thanks,
Miklos
---
Miklos Szeredi (12):
aio: fix async fsync creds
fs_parse: fix fs_param_v_optional handling
vfs: verify param type in vfs_parse_sb_flag()
uapi: deprecate STATX_ALL
statx: don't clear STATX_ATIME on SB_RDONLY
utimensat: AT_EMPTY_PATH support
f*xattr: allow O_PATH descriptors
vfs: allow unprivileged whiteout creation
fs_parser: "string" with missing value is a "flag"
vfs: don't parse forbidden flags
vfs: don't parse "posixacl" option
vfs: don't parse "silent" option
fs/aio.c | 8 ++++
fs/char_dev.c | 3 ++
fs/fs_context.c | 72 ++++++++++++---------------------
fs/fs_parser.c | 19 ++++-----
fs/namei.c | 17 ++------
fs/stat.c | 4 +-
fs/utimes.c | 6 ++-
fs/xattr.c | 8 ++--
include/linux/device_cgroup.h | 3 ++
include/linux/fs_parser.h | 1 -
include/uapi/linux/stat.h | 11 ++++-
samples/vfs/test-statx.c | 2 +-
tools/include/uapi/linux/stat.h | 11 ++++-
13 files changed, 82 insertions(+), 83 deletions(-)
--
2.21.0
next reply other threads:[~2019-11-28 15:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 15:59 Miklos Szeredi [this message]
2019-11-28 15:59 ` [PATCH 01/12] aio: fix async fsync creds Miklos Szeredi
2019-12-13 9:32 ` Miklos Szeredi
2020-05-04 8:05 ` Avi Kivity
2019-11-28 15:59 ` [PATCH 02/12] fs_parse: fix fs_param_v_optional handling Miklos Szeredi
2019-11-29 11:31 ` Andrew Price
2019-11-29 14:43 ` Miklos Szeredi
2019-11-29 15:56 ` Andrew Price
2019-12-16 23:28 ` Al Viro
2019-12-17 1:18 ` Al Viro
2019-12-17 3:27 ` Al Viro
2019-11-28 15:59 ` [PATCH 03/12] vfs: verify param type in vfs_parse_sb_flag() Miklos Szeredi
2019-11-28 15:59 ` [PATCH 04/12] uapi: deprecate STATX_ALL Miklos Szeredi
2019-11-28 15:59 ` [PATCH 05/12] statx: don't clear STATX_ATIME on SB_RDONLY Miklos Szeredi
2019-11-28 15:59 ` [PATCH 06/12] utimensat: AT_EMPTY_PATH support Miklos Szeredi
2019-11-28 15:59 ` [PATCH 07/12] f*xattr: allow O_PATH descriptors Miklos Szeredi
2019-11-28 15:59 ` [PATCH 08/12] vfs: allow unprivileged whiteout creation Miklos Szeredi
2019-12-17 3:51 ` Al Viro
2019-12-17 4:22 ` Miklos Szeredi
2019-11-28 15:59 ` [PATCH 09/12] fs_parser: "string" with missing value is a "flag" Miklos Szeredi
2019-12-17 17:32 ` Al Viro
2019-12-17 18:31 ` Al Viro
2019-11-28 15:59 ` [PATCH 10/12] vfs: don't parse forbidden flags Miklos Szeredi
2019-11-28 15:59 ` [PATCH 11/12] vfs: don't parse "posixacl" option Miklos Szeredi
2019-12-17 3:42 ` Al Viro
2019-12-17 4:18 ` Miklos Szeredi
2019-12-17 4:28 ` Al Viro
2019-11-28 15:59 ` [PATCH 12/12] vfs: don't parse "silent" option Miklos Szeredi
2019-12-17 3:37 ` Al Viro
2019-12-17 4:12 ` Miklos Szeredi
2019-12-17 4:16 ` Miklos Szeredi
2019-12-17 4:19 ` Al Viro
2019-12-17 4:23 ` Miklos Szeredi
2019-12-17 4:28 ` Miklos Szeredi
2019-12-17 4:17 ` Al Viro
2019-12-13 9:33 ` [PATCH 00/12] various vfs patches Miklos Szeredi
2019-12-16 23:13 ` Al Viro
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=20191128155940.17530-1-mszeredi@redhat.com \
--to=mszeredi@redhat.com \
--cc=linux-fsdevel@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).