From: Carlos Maiolino <cmaiolino@redhat.com>
To: linux-fsdevel@vger.kernel.org
Cc: vgoyal@redhat.com
Subject: Re: [PATCH] overlayfs: Do d_type check only if work dir creation was successful
Date: Mon, 23 May 2016 14:01:50 +0200 [thread overview]
Message-ID: <20160523120150.GB21456@redhat.com> (raw)
In-Reply-To: <20160520130426.GA31667@redhat.com>
Hi Vivek.
On Fri, May 20, 2016 at 09:04:26AM -0400, Vivek Goyal wrote:
> d_type check requires successful creation of workdir as iterates
> through work dir and expects work dir to be present in it. If that's
> not the case, this check will always return d_type not supported even
> if underlying filesystem might be supporting it.
>
ovl_check_d_type_supported, will call iterate_dir(), which is supposed to return
-ENOENT if the work dir is not present AFAICT, isn't that enough to detect if
work dir is present and handle it accordingly?
I recently started to learn overlay code, so my apologies if my above comment is
not true.
Cheers
> So don't do this check if work dir creation failed in previous step.
>
> Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
> ---
> fs/overlayfs/super.c | 19 +++++++++++--------
> 1 file changed, 11 insertions(+), 8 deletions(-)
>
> diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c
> index 791235e..48234425 100644
> --- a/fs/overlayfs/super.c
> +++ b/fs/overlayfs/super.c
> @@ -1064,16 +1064,19 @@ static int ovl_fill_super(struct super_block *sb, void *data, int silent)
> /*
> * Upper should support d_type, else whiteouts are visible.
> * Given workdir and upper are on same fs, we can do
> - * iterate_dir() on workdir.
> + * iterate_dir() on workdir. This check requires successful
> + * creation of workdir in previous step.
> */
> - err = ovl_check_d_type_supported(&workpath);
> - if (err < 0)
> - goto out_put_workdir;
> + if (ufs->workdir) {
> + err = ovl_check_d_type_supported(&workpath);
> + if (err < 0)
> + goto out_put_workdir;
>
> - if (!err) {
> - pr_err("overlayfs: upper fs needs to support d_type.\n");
> - err = -EINVAL;
> - goto out_put_workdir;
> + if (!err) {
> + pr_err("overlayfs: upper fs needs to support d_type.\n");
> + err = -EINVAL;
> + goto out_put_workdir;
> + }
> }
> }
>
> --
> 2.7.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Carlos
next prev parent reply other threads:[~2016-05-23 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 13:04 [PATCH] overlayfs: Do d_type check only if work dir creation was successful Vivek Goyal
2016-05-23 12:01 ` Carlos Maiolino [this message]
2016-05-23 14:04 ` Vivek Goyal
2016-05-30 20:10 ` Carlos Maiolino
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=20160523120150.GB21456@redhat.com \
--to=cmaiolino@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=vgoyal@redhat.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).