From: Carlos Maiolino <cmaiolino@redhat.com>
To: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] overlayfs: Do d_type check only if work dir creation was successful
Date: Mon, 30 May 2016 22:10:56 +0200 [thread overview]
Message-ID: <20160530201056.GA11155@redhat.com> (raw)
In-Reply-To: <20160523140412.GA4931@redhat.com>
On Mon, May 23, 2016 at 10:04:12AM -0400, Vivek Goyal wrote:
> On Mon, May 23, 2016 at 02:01:50PM +0200, Carlos Maiolino wrote:
> > 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?
>
> Hi Carlos,
>
> So there is directory "work" under user specified workdir. Say user
> specified "overlaywork" as workdir, then we are listing contents of "
> overlaywork" and which should find "work" underneath it. Even if "work"
> creation failed, "." and ".." are found and returned and their types
> are returned as DT_DIR (despite the fact that filesystem does not support
> d_type").
>
> So in short, I am not getting -ENOENT if work dir creation failed.
>
> Thanks
> Vivek
>
Hi Vivek, my apologies for my delay, I had some problems with my mail filter and
I missed your reply before.
Thanks for the explanation, it makes sense to me, you can add:
Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>
Cheers
--
Carlos
prev parent reply other threads:[~2016-05-30 20:11 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
2016-05-23 14:04 ` Vivek Goyal
2016-05-30 20:10 ` Carlos Maiolino [this message]
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=20160530201056.GA11155@redhat.com \
--to=cmaiolino@redhat.com \
--cc=linux-fsdevel@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).