[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190625181733.GG5375@magnolia>
Date: Tue, 25 Jun 2019 11:17:33 -0700
From: "Darrick J. Wong" <darrick.wong@...cle.com>
To: dsterba@...e.cz, matthew.garrett@...ula.com, yuchao0@...wei.com,
tytso@....edu, shaggy@...nel.org, ard.biesheuvel@...aro.org,
josef@...icpanda.com, clm@...com, adilger.kernel@...ger.ca,
jk@...abs.org, jack@...e.com, dsterba@...e.com, jaegeuk@...nel.org,
viro@...iv.linux.org.uk, cluster-devel@...hat.com,
jfs-discussion@...ts.sourceforge.net, linux-efi@...r.kernel.org,
Jan Kara <jack@...e.cz>, reiserfs-devel@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net, linux-xfs@...r.kernel.org,
linux-nilfs@...r.kernel.org, linux-mtd@...ts.infradead.org,
ocfs2-devel@....oracle.com, linux-fsdevel@...r.kernel.org,
linux-ext4@...r.kernel.org, linux-btrfs@...r.kernel.org
Subject: Re: [PATCH 1/4] vfs: create a generic checking function for
FS_IOC_SETFLAGS
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@...cle.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@...e.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
Powered by blists - more mailing lists