Linux Overlay Filesystem development
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>, linux-unionfs@vger.kernel.org
Subject: Re: [PATCH v2 0/5] Prep patches for porting overlayfs to new mount api
Date: Tue, 20 Jun 2023 11:26:37 +0200	[thread overview]
Message-ID: <20230620-emblem-umgeladen-7d5c2cc0a8db@brauner> (raw)
In-Reply-To: <20230617084702.2468470-1-amir73il@gmail.com>

On Sat, Jun 17, 2023 at 11:46:57AM +0300, Amir Goldstein wrote:
> 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 for splitting some work into preparatory patches. I'm not sure
how worthwhile this actually is given they aren't marked as backports
for LTS releases so the overall delta ould still the same between LTSes
and mainline but it might make bisection easier.

  parent reply	other threads:[~2023-06-20  9:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-17  8:46 [PATCH v2 0/5] Prep patches for porting overlayfs to new mount api Amir Goldstein
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 ` Christian Brauner [this message]
2023-06-20  9:46   ` [PATCH v2 0/5] Prep patches for porting overlayfs to new mount api 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=20230620-emblem-umgeladen-7d5c2cc0a8db@brauner \
    --to=brauner@kernel.org \
    --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