From: Vivek Goyal <vgoyal@redhat.com>
To: linux-unionfs@vger.kernel.org
Cc: miklos@szeredi.hu, amir73il@gmail.com, vgoyal@redhat.com
Subject: [PATCH v2 2/4] ovl: Do not check for redirect if this is last layer
Date: Fri, 9 Mar 2018 15:44:42 -0500 [thread overview]
Message-ID: <20180309204444.13237-3-vgoyal@redhat.com> (raw)
In-Reply-To: <20180309204444.13237-1-vgoyal@redhat.com>
If we are looking in last layer, then there should not be any need to
process redirect. redirect information is used only for lookup in next
lower layer and there is no more lower layer to look into. So no need
to process redirects.
IOW, ignore redirects on lowest layer.
Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Reviewed-by: Amir Goldstein <amir73il@gmail.com>
---
fs/overlayfs/namei.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/fs/overlayfs/namei.c b/fs/overlayfs/namei.c
index 78798367c4f0..e27afd8d378a 100644
--- a/fs/overlayfs/namei.c
+++ b/fs/overlayfs/namei.c
@@ -248,7 +248,10 @@ static int ovl_lookup_single(struct dentry *base, struct ovl_lookup_data *d,
goto out;
}
d->is_dir = true;
- if (!d->last && ovl_is_opaquedir(this)) {
+ if (d->last)
+ goto out;
+
+ if (ovl_is_opaquedir(this)) {
d->stop = d->opaque = true;
goto out;
}
--
2.13.6
next prev parent reply other threads:[~2018-03-09 20:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 20:44 [PATCH v2 0/4] ovl: Bunch of ovl_lookup() path fixes Vivek Goyal
2018-03-09 20:44 ` [PATCH v2 1/4] ovl: Set d->last properly during lookup Vivek Goyal
2018-03-29 9:50 ` Miklos Szeredi
2018-03-09 20:44 ` Vivek Goyal [this message]
2018-03-09 20:44 ` [PATCH v2 3/4] ovl: set d->is_dir and d->opaque for last path element Vivek Goyal
2018-03-09 20:44 ` [PATCH v2 4/4] ovl: fix lookup with middle layer opaque dir and absolute path redirects Vivek Goyal
2018-03-10 20:07 ` Amir Goldstein
2018-03-12 12:51 ` Vivek Goyal
2018-03-12 13:01 ` Amir Goldstein
2018-03-12 14:30 ` [PATCH v2.1 " Vivek Goyal
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=20180309204444.13237-3-vgoyal@redhat.com \
--to=vgoyal@redhat.com \
--cc=amir73il@gmail.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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