From: Eric Biggers <ebiggers@kernel.org>
To: "Darrick J . Wong" <darrick.wong@oracle.com>
Cc: linux-fsdevel@vger.kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>,
linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH 0/3] f2fs: use generic helpers for FS_IOC_{SETFLAGS, FSSETXATTR}
Date: Mon, 1 Jul 2019 13:26:27 -0700 [thread overview]
Message-ID: <20190701202630.43776-1-ebiggers@kernel.org> (raw)
This series converts f2fs to use the new VFS helper functions that check
the parameters of the FS_IOC_SETFLAGS and FS_IOC_FSSETXATTR ioctls.
This applies to the merge of the f2fs/dev and xfs/vfs-for-next branches:
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/log/?h=dev
https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git/log/?h=vfs-for-next
i.e., this series will apply to mainline after these two branches get
merged into it for 5.3. Don't apply it to the f2fs tree by itself yet.
See: https://lore.kernel.org/lkml/20190701110603.5abcbb2c@canb.auug.org.au/T/#u
Eric Biggers (3):
f2fs: use generic checking and prep function for FS_IOC_SETFLAGS
f2fs: use generic checking function for FS_IOC_FSSETXATTR
f2fs: remove redundant check from f2fs_setflags_common()
fs/f2fs/file.c | 63 ++++++++++++++++++--------------------------------
1 file changed, 23 insertions(+), 40 deletions(-)
--
2.22.0.410.gd8fdbe21b5-goog
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: "Darrick J . Wong" <darrick.wong@oracle.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org
Subject: [PATCH 0/3] f2fs: use generic helpers for FS_IOC_{SETFLAGS,FSSETXATTR}
Date: Mon, 1 Jul 2019 13:26:27 -0700 [thread overview]
Message-ID: <20190701202630.43776-1-ebiggers@kernel.org> (raw)
This series converts f2fs to use the new VFS helper functions that check
the parameters of the FS_IOC_SETFLAGS and FS_IOC_FSSETXATTR ioctls.
This applies to the merge of the f2fs/dev and xfs/vfs-for-next branches:
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git/log/?h=dev
https://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git/log/?h=vfs-for-next
i.e., this series will apply to mainline after these two branches get
merged into it for 5.3. Don't apply it to the f2fs tree by itself yet.
See: https://lore.kernel.org/lkml/20190701110603.5abcbb2c@canb.auug.org.au/T/#u
Eric Biggers (3):
f2fs: use generic checking and prep function for FS_IOC_SETFLAGS
f2fs: use generic checking function for FS_IOC_FSSETXATTR
f2fs: remove redundant check from f2fs_setflags_common()
fs/f2fs/file.c | 63 ++++++++++++++++++--------------------------------
1 file changed, 23 insertions(+), 40 deletions(-)
--
2.22.0.410.gd8fdbe21b5-goog
next reply other threads:[~2019-07-01 20:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 20:26 Eric Biggers [this message]
2019-07-01 20:26 ` [PATCH 0/3] f2fs: use generic helpers for FS_IOC_{SETFLAGS,FSSETXATTR} Eric Biggers
2019-07-01 20:26 ` [f2fs-dev] [PATCH 1/3] f2fs: use generic checking and prep function for FS_IOC_SETFLAGS Eric Biggers
2019-07-01 20:26 ` Eric Biggers
2019-07-03 1:58 ` [f2fs-dev] " Chao Yu
2019-07-03 1:58 ` Chao Yu
2019-07-07 20:41 ` [f2fs-dev] " Darrick J. Wong
2019-07-07 20:41 ` Darrick J. Wong
2019-07-01 20:26 ` [f2fs-dev] [PATCH 2/3] f2fs: use generic checking function for FS_IOC_FSSETXATTR Eric Biggers
2019-07-01 20:26 ` Eric Biggers
2019-07-03 1:58 ` [f2fs-dev] " Chao Yu
2019-07-03 1:58 ` Chao Yu
2019-07-07 20:41 ` [f2fs-dev] " Darrick J. Wong
2019-07-07 20:41 ` Darrick J. Wong
2019-07-01 20:26 ` [f2fs-dev] [PATCH 3/3] f2fs: remove redundant check from f2fs_setflags_common() Eric Biggers
2019-07-01 20:26 ` Eric Biggers
2019-07-03 1:58 ` [f2fs-dev] " Chao Yu
2019-07-03 1:58 ` Chao Yu
2019-07-07 20:42 ` [f2fs-dev] " Darrick J. Wong
2019-07-07 20:42 ` Darrick J. Wong
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=20190701202630.43776-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=darrick.wong@oracle.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.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 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.