From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
xfs <linux-xfs@vger.kernel.org>,
linux-ext4 <linux-ext4@vger.kernel.org>
Subject: [ANNOUNCE RESEND] xfs-linux: vfs-for-next updated to 7e328e5930ad
Date: Thu, 4 Jul 2019 08:07:58 -0700 [thread overview]
Message-ID: <20190704150758.GD5164@magnolia> (raw)
Hi folks,
The vfs-for-next branch of the xfs-linux repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git
has (not) been updated. This is a resend of previous announcements
about the SETFLAGS and FSSETXATTR refactoring that I've started for 5.3
and will continue for 5.4 so that these ioctls will have more consistent
behavior with the filesystems that originally created them.
The new head of the vfs-for-next branch is commit:
7e328e5930ad mm/fs: don't allow writes to immutable files
New Commits:
Darrick J. Wong (6):
[5aca284210ce] vfs: create a generic checking and prep function for FS_IOC_SETFLAGS
[7b0e492e6b80] vfs: create a generic checking function for FS_IOC_FSSETXATTR
[f991492ed110] vfs: teach vfs_ioc_fssetxattr_check to check project id info
[ca29be753445] vfs: teach vfs_ioc_fssetxattr_check to check extent size hints
[dbc77f31e58b] vfs: only allow FSSETXATTR to set DAX flag on files and dirs
[7e328e5930ad] mm/fs: don't allow writes to immutable files
Code Diffstat:
fs/attr.c | 13 ++---
fs/btrfs/ioctl.c | 30 ++++------
fs/efivarfs/file.c | 26 ++++++---
fs/ext2/ioctl.c | 16 ++----
fs/ext4/ioctl.c | 51 +++++------------
fs/gfs2/file.c | 42 +++++++++-----
fs/hfsplus/ioctl.c | 21 ++++---
fs/inode.c | 86 +++++++++++++++++++++++++++++
fs/jfs/ioctl.c | 22 +++-----
fs/nilfs2/ioctl.c | 9 +--
fs/ocfs2/ioctl.c | 13 +----
fs/orangefs/file.c | 37 ++++++++++---
fs/reiserfs/ioctl.c | 10 ++--
fs/ubifs/ioctl.c | 13 +----
fs/xfs/xfs_ioctl.c | 154 +++++++++++++++++++++++-----------------------------
include/linux/fs.h | 12 ++++
mm/filemap.c | 3 +
mm/memory.c | 4 ++
mm/mmap.c | 8 ++-
19 files changed, 319 insertions(+), 251 deletions(-)
reply other threads:[~2019-07-04 15:08 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=20190704150758.GD5164@magnolia \
--to=darrick.wong@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@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 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).