From: Amir Goldstein <amir73il@gmail.com>
To: Xiao Yang <yangx.jy@cn.fujitsu.com>
Cc: overlayfs <linux-unionfs@vger.kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Christoph Hellwig <hch@infradead.org>,
fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH] ovl: Support FS_IOC_[SG]ETFLAGS and FS_IOC_FS[SG]ETXATTR ioctls on directories
Date: Tue, 22 Sep 2020 15:01:29 +0300 [thread overview]
Message-ID: <CAOQ4uxg-4xOSVxkLZrH_zrd9054z+SH_+YdcPnT3PVNYogJ3gw@mail.gmail.com> (raw)
In-Reply-To: <5F69B2A4.2050407@cn.fujitsu.com>
On Tue, Sep 22, 2020 at 11:15 AM Xiao Yang <yangx.jy@cn.fujitsu.com> wrote:
>
> On 2020/9/21 17:09, Amir Goldstein wrote:
> > On Mon, Sep 21, 2020 at 11:55 AM Xiao Yang<yangx.jy@cn.fujitsu.com> wrote:
> >> On 2020/9/21 16:17, Amir Goldstein wrote:
> >>> On Mon, Sep 21, 2020 at 10:41 AM Xiao Yang<yangx.jy@cn.fujitsu.com> wrote:
> >>>> Factor out ovl_ioctl() and ovl_compat_ioctl() and take use of them for
> >>>> directories.
> >>>>
> >>>> Signed-off-by: Xiao Yang<yangx.jy@cn.fujitsu.com>
> >>>> ---
> >>> This change is buggy. I had already posted it and self NACKed myself [1].
> >>>
> >>> You can find an hopefully non-buggy version of it on my ovl-shutdown [2] branch.
> >>>
> >>> As long as you are changing ovl_ioctl(), please also take the second
> >>> commit on that
> >>> branch to replace the open coded capability check with the
> >>> vfs_ioc_setflags_prepare()
> >>> generic helper.
> >> Hi Amir,
> >>
> >> Thanks a lot for your quick reply. :-)
> >> I will try to read and understand the metioned patches on your
> >> ovl-shutdown branch.
> > Please also verify my claim in the patch commit message, that the
> > the test result of xfstest generic/079 changes from "notrun" to "success".
> Hi Amir,
>
> With your patches, I have confirmed that generic/079 actually changed from
> "notrun" to "success". Besides, one minor issue:
> Could we avoid the following compiler warning?
> -------------------------------------------------
> fs/overlayfs/readdir.c: In function ‘ovl_dir_real_file’:
> fs/overlayfs/readdir.c:883:37: warning: passing argument 1 of
> ‘ovl_dir_open_realfile’ discards ‘const’ qualifier from pointer target
> type [-Wdiscarded-qualifiers]
> 883 | realfile = ovl_dir_open_realfile(file, &upperpath);
> | ^~~~
> fs/overlayfs/readdir.c:842:56: note: expected ‘struct file *’ but
> argument is of type ‘const struct file *’
> 842 | static struct file *ovl_dir_open_realfile(struct file *file,
> | ~~~~~~~~~~~~~^~~~
> -------------------------------------------------
>
Shouldn't be a problem to change ovl_dir_open_realfile()
to take a const struct file * argument I think.
Thanks,
Amir.
next prev parent reply other threads:[~2020-09-22 12:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 7:21 [PATCH] ovl: Support FS_IOC_[SG]ETFLAGS and FS_IOC_FS[SG]ETXATTR ioctls on directories Xiao Yang
2020-09-21 8:17 ` Amir Goldstein
2020-09-21 8:55 ` Xiao Yang
2020-09-21 9:09 ` Amir Goldstein
2020-09-22 8:15 ` Xiao Yang
2020-09-22 12:01 ` Amir Goldstein [this message]
2020-09-25 15:12 ` Xiao Yang
2020-09-25 17:49 ` Amir Goldstein
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=CAOQ4uxg-4xOSVxkLZrH_zrd9054z+SH_+YdcPnT3PVNYogJ3gw@mail.gmail.com \
--to=amir73il@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=yangx.jy@cn.fujitsu.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).