From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Christian Brauner <brauner@kernel.org>, linux-unionfs@vger.kernel.org
Subject: [PATCH 0/4] ovl: new mount options lowerdir+,datadir+
Date: Mon, 30 Oct 2023 14:04:15 +0200 [thread overview]
Message-ID: <20231030120419.478228-1-amir73il@gmail.com> (raw)
Miklos,
As discussed, here are the patches for the new mount options.
- Only string format is supported
- Legacy lowerdir= cannot be mixed with new lowerdir+,datadir+
- lowerdir+,datadir+ are not escaped
- lowerdir,upperdir,workdir are escaped as always
I did not find a good reason to change escaping of upperdir,workdir.
We can skip escaping when we add support for path format.
Wrote some xfstests [1].
Thanks,
Amir.
[1] https://github.com/amir73il/xfstests/commits/ovl-lowerdir-add
Amir Goldstein (4):
ovl: remove unused code in lowerdir param parsing
ovl: store and show the user provided lowerdir mount option
ovl: refactor layer parsing helpers
ovl: add support for appending lowerdirs one by one
fs/overlayfs/params.c | 317 ++++++++++++++++++++++--------------------
fs/overlayfs/params.h | 1 +
fs/overlayfs/super.c | 5 +-
3 files changed, 173 insertions(+), 150 deletions(-)
--
2.34.1
next reply other threads:[~2023-10-30 12:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 12:04 Amir Goldstein [this message]
2023-10-30 12:04 ` [PATCH 1/4] ovl: remove unused code in lowerdir param parsing Amir Goldstein
2023-10-30 12:04 ` [PATCH 2/4] ovl: store and show the user provided lowerdir mount option Amir Goldstein
2023-10-30 12:04 ` [PATCH 3/4] ovl: refactor layer parsing helpers Amir Goldstein
2023-10-30 15:36 ` Miklos Szeredi
2023-10-30 17:41 ` Amir Goldstein
2023-10-30 12:04 ` [PATCH 4/4] ovl: add support for appending lowerdirs one by one Amir Goldstein
2023-10-30 13:06 ` Amir Goldstein
2023-10-30 15:41 ` [PATCH 0/4] ovl: new mount options lowerdir+,datadir+ Miklos Szeredi
2023-10-30 18:45 ` 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=20231030120419.478228-1-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=brauner@kernel.org \
--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