Linux Overlay Filesystem development
 help / color / mirror / Atom feed
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 v2 0/5] Prep patches for porting overlayfs to new mount api
Date: Sat, 17 Jun 2023 11:46:57 +0300	[thread overview]
Message-ID: <20230617084702.2468470-1-amir73il@gmail.com> (raw)

Miklos,

Following some more cleanup patches that make Christian's new mount api
patches smaller and easier to review.

I had rebased Christain's patches over these cleanups and pushed the
result to github branch fs-overlayfs-mount_api [1].

The v1 prep patches had a bug with xino option parsing that resulted in
some tests being skipped (not failing) and I had only noticed the
skipped test after posting v1.

The v2 prep patches + new mount api patches have passed all the tests
with no new tests skipped.

In addition to running the tests with the default kernel config, I also
ran the tests with the following non-default configs (individually):

1) CONFIG_OVERLAY_FS_REDIRECT_DIR=y
2) CONFIG_OVERLAY_FS_REDIRECT_ALWAYS_FOLLOW=n
3) CONFIG_OVERLAY_FS_XINO_AUTO=y


Thanks.
Amir.

Changes since v1:
- Fix xino opt name table vs. enum order
- Add cleanup patch for xino
- Add cleanup of share_whiteout state
- Add cleanup patch for ovl_get_root()

[1] https://github.com/amir73il/linux/commits/fs-overlayfs-mount_api

Amir Goldstein (5):
  ovl: negate the ofs->share_whiteout boolean
  ovl: clarify ovl_get_root() semantics
  ovl: pass ovl_fs to xino helpers
  ovl: store enum redirect_mode in config instead of a string
  ovl: factor out ovl_parse_options() helper

 Documentation/filesystems/overlayfs.rst |   9 +-
 fs/overlayfs/dir.c                      |   6 +-
 fs/overlayfs/inode.c                    |  18 +-
 fs/overlayfs/namei.c                    |   6 +-
 fs/overlayfs/overlayfs.h                |  63 ++--
 fs/overlayfs/ovl_entry.h                |   8 +-
 fs/overlayfs/readdir.c                  |  19 +-
 fs/overlayfs/super.c                    | 364 +++++++++++++-----------
 fs/overlayfs/util.c                     |   7 -
 9 files changed, 274 insertions(+), 226 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-06-17  8:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-17  8:46 Amir Goldstein [this message]
2023-06-17  8:46 ` [PATCH v2 1/5] ovl: negate the ofs->share_whiteout boolean Amir Goldstein
2023-06-20  9:20   ` Christian Brauner
2023-06-17  8:46 ` [PATCH v2 2/5] ovl: clarify ovl_get_root() semantics Amir Goldstein
2023-06-20  9:21   ` Christian Brauner
2023-06-17  8:47 ` [PATCH v2 3/5] ovl: pass ovl_fs to xino helpers Amir Goldstein
2023-06-20  9:21   ` Christian Brauner
2023-06-17  8:47 ` [PATCH v2 4/5] ovl: store enum redirect_mode in config instead of a string Amir Goldstein
2023-06-20  8:48   ` Miklos Szeredi
2023-06-20  8:50     ` Miklos Szeredi
2023-06-20  9:23   ` Christian Brauner
2023-06-17  8:47 ` [PATCH v2 5/5] ovl: factor out ovl_parse_options() helper Amir Goldstein
2023-06-20  9:19   ` Christian Brauner
2023-06-20  9:26 ` [PATCH v2 0/5] Prep patches for porting overlayfs to new mount api Christian Brauner
2023-06-20  9:46   ` Amir Goldstein
2023-06-20 10:12     ` Christian Brauner

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=20230617084702.2468470-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