From: Vyacheslav Yurkov <uvv.mail@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>, Amir Goldstein <amir73il@gmail.com>
Cc: linux-unionfs@vger.kernel.org,
Vyacheslav Yurkov <Vyacheslav.Yurkov@bruker.com>
Subject: [PATCH v3 1/3] ovl: disable decoding null uuid with redirect dir
Date: Thu, 27 May 2021 19:45:45 +0200 [thread overview]
Message-ID: <20210527174547.109269-1-uvv.mail@gmail.com> (raw)
From: Vyacheslav Yurkov <Vyacheslav.Yurkov@bruker.com>
Currently decoding origin with lower null uuid is not allowed unless user
opted-in to one of the new features that require following the lower inode
of non-dir upper (index, xino, metacopy). Now we add redirect_dir too to
that feature list.
Signed-off-by: Vyacheslav Yurkov <Vyacheslav.Yurkov@bruker.com>
---
fs/overlayfs/super.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c
index b01d4147520d..97ea35fdd933 100644
--- a/fs/overlayfs/super.c
+++ b/fs/overlayfs/super.c
@@ -1600,7 +1600,7 @@ static bool ovl_lower_uuid_ok(struct ovl_fs *ofs, const uuid_t *uuid)
* lower inode of non-dir upper.
*/
if (!ofs->config.index && !ofs->config.metacopy &&
- ofs->config.xino != OVL_XINO_ON &&
+ !ofs->config.redirect_dir && ofs->config.xino != OVL_XINO_ON &&
uuid_is_null(uuid))
return false;
--
2.25.1
next reply other threads:[~2021-05-27 17:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 17:45 Vyacheslav Yurkov [this message]
2021-05-27 17:45 ` [PATCH v3 2/3] ovl: add ovl_allow_offline_changes() helper Vyacheslav Yurkov
2021-05-27 17:45 ` [PATCH v3 3/3] ovl: do not set overlay.opaque for new directories Vyacheslav Yurkov
2021-05-28 11:38 ` Amir Goldstein
2021-06-01 6:53 ` Yurkov, Vyacheslav
2021-06-01 8:33 ` Amir Goldstein
2021-06-01 16:29 ` Yurkov, Vyacheslav
2021-06-01 18:29 ` Amir Goldstein
2021-06-04 12:32 ` Amir Goldstein
2021-06-04 14:50 ` Yurkov, Vyacheslav
2021-06-04 19:18 ` Amir Goldstein
2021-07-19 14:29 ` Miklos Szeredi
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=20210527174547.109269-1-uvv.mail@gmail.com \
--to=uvv.mail@gmail.com \
--cc=Vyacheslav.Yurkov@bruker.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;
as well as URLs for NNTP newsgroup(s).