From: Darrick J. Wong <darrick.wong@oracle.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 1/4] vfs: create a generic checking function for FS_IOC_SETFLAGS
Date: Tue, 25 Jun 2019 11:17:33 -0700 [thread overview]
Message-ID: <20190625181733.GG5375@magnolia> (raw)
In-Reply-To: <20190625171254.GT8917@twin.jikos.cz>
On Tue, Jun 25, 2019 at 07:12:54PM +0200, David Sterba wrote:
> On Fri, Jun 21, 2019 at 04:56:21PM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> >
> > Create a generic checking function for the incoming FS_IOC_SETFLAGS flag
> > values so that we can standardize the implementations that follow ext4's
> > flag values.
>
> I checked a few samples what's the type of the flags, there are unsigned
> types while the proposed VFS functions take signed type.
>
> > +int vfs_ioc_setflags_check(struct inode *inode, int oldflags, int flags);
>
> Specifically ext4 uses unsigned type and his was the original API that
> got copied so I'd think that it should unsigned everywhere.
Yeah, I'll change it.
> > fs/btrfs/ioctl.c | 13 +++++--------
>
> For the btrfs bits
>
> Acked-by: David Sterba <dsterba@suse.com>
>
> and besides the signedness, the rest of the changes look good to me.
Thanks for the look around! I'll have a new revision with all changes
out by the end of the day. :)
--D
next prev parent reply other threads:[~2019-06-25 18:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 23:56 [Cluster-devel] [PATCH v2 0/4] vfs: clean up SETFLAGS and FSSETXATTR option processing Darrick J. Wong
2019-06-21 23:56 ` [Cluster-devel] [PATCH 1/4] vfs: create a generic checking function for FS_IOC_SETFLAGS Darrick J. Wong
2019-06-25 10:54 ` Christoph Hellwig
2019-06-25 17:12 ` David Sterba
2019-06-25 18:17 ` Darrick J. Wong [this message]
2019-06-21 23:56 ` [Cluster-devel] [PATCH 2/4] vfs: create a generic checking function for FS_IOC_FSSETXATTR Darrick J. Wong
2019-06-25 10:57 ` Christoph Hellwig
2019-06-25 17:02 ` David Sterba
2019-06-25 17:16 ` Darrick J. Wong
2019-06-25 17:33 ` David Sterba
2019-06-21 23:56 ` [Cluster-devel] [PATCH 3/4] fs: teach vfs_ioc_fssetxattr_check to check project id info Darrick J. Wong
2019-06-25 10:57 ` Christoph Hellwig
2019-06-21 23:56 ` [Cluster-devel] [PATCH 4/4] vfs: teach vfs_ioc_fssetxattr_check to check extent size hints Darrick J. Wong
2019-06-25 10:58 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2019-06-11 4:45 [Cluster-devel] [PATCH 0/4] vfs: clean up SETFLAGS and FSSETXATTR option processing Darrick J. Wong
2019-06-11 4:45 ` [Cluster-devel] [PATCH 1/4] vfs: create a generic checking function for FS_IOC_SETFLAGS 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=20190625181733.GG5375@magnolia \
--to=darrick.wong@oracle.com \
/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).