From: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>,
Amir Goldstein <amir73il@gmail.com>,
Vivek Goyal <vgoyal@redhat.com>,
linux-unionfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/2] ovl introduce "uuid=off"
Date: Thu, 24 Sep 2020 19:37:53 +0300 [thread overview]
Message-ID: <20200924163755.7717-1-ptikhomirov@virtuozzo.com> (raw)
This is a v3 of:
ovl: introduce new "index=nouuid" option for inodes index feature
Changes in v3: rebase to overlayfs-next, replace uuid with null in file
handles, propagate ovl_fs to needed functions in a separate patch, add
separate bool "uuid=on/off" option, fix numfs check fallback, add a note
to docs.
CC: Amir Goldstein <amir73il@gmail.com>
CC: Vivek Goyal <vgoyal@redhat.com>
CC: Miklos Szeredi <miklos@szeredi.hu>
CC: linux-unionfs@vger.kernel.org
CC: linux-kernel@vger.kernel.org
Signed-off-by: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
Pavel Tikhomirov (2):
ovl: propagate ovl_fs to ovl_decode_real_fh and ovl_encode_real_fh
ovl: introduce new "uuid=off" option for inodes index feature
Documentation/filesystems/overlayfs.rst | 6 ++++++
fs/overlayfs/Kconfig | 17 +++++++++++++++++
fs/overlayfs/copy_up.c | 25 ++++++++++++++-----------
fs/overlayfs/export.c | 10 ++++++----
fs/overlayfs/namei.c | 24 ++++++++++++++----------
fs/overlayfs/overlayfs.h | 14 ++++++++------
fs/overlayfs/ovl_entry.h | 1 +
fs/overlayfs/super.c | 25 +++++++++++++++++++++++++
fs/overlayfs/util.c | 3 ++-
9 files changed, 93 insertions(+), 32 deletions(-)
--
2.26.2
next reply other threads:[~2020-09-24 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 16:37 Pavel Tikhomirov [this message]
2020-09-24 16:37 ` [PATCH v3 1/2] ovl: propagate ovl_fs to ovl_decode_real_fh and ovl_encode_real_fh Pavel Tikhomirov
2020-09-24 16:37 ` [PATCH v3 2/2] ovl: introduce new "uuid=off" option for inodes index feature Pavel Tikhomirov
2020-09-24 17:02 ` Amir Goldstein
2020-09-25 8:39 ` Pavel Tikhomirov
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=20200924163755.7717-1-ptikhomirov@virtuozzo.com \
--to=ptikhomirov@virtuozzo.com \
--cc=amir73il@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--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).