public inbox for linux-unionfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Alexander Larsson <alexl@redhat.com>, linux-unionfs@vger.kernel.org
Subject: [PATCH 0/5] Overlayfs lazy lookup of lowerdata
Date: Wed, 12 Apr 2023 16:54:07 +0300	[thread overview]
Message-ID: <20230412135412.1684197-1-amir73il@gmail.com> (raw)

Miklos,

Here are the patches discussed earlier at [1].
They are based on the already posted cleanup series [2].

This work is motivated by Alexander's composefs use case.
Alexander has been developing and testing his fsverity patches over
my lazy-lowerdata-lookup branch [3].

Alexander has also written tests for lazy lowerdata lookup [4].

Thanks,
Amir.

[1] https://lore.kernel.org/linux-unionfs/CAOQ4uxich227fP7bGSCNqx-JX5h36O-MLwqPoy0r33tuH=z2cA@mail.gmail.com/
[2] https://lore.kernel.org/linux-unionfs/20230408164302.1392694-1-amir73il@gmail.com/
[3] https://github.com/amir73il/linux/commits/ovl-lazy-lowerdata
[4] https://github.com/amir73il/xfstests/commits/ovl-lazy-lowerdata


Amir Goldstein (5):
  ovl: remove unneeded goto instructions
  ovl: introduce data-only lower layers
  ovl: implement lookup in data-only layers
  ovl: prepare for lazy lookup of lowerdata inode
  ovl: implement lazy lookup of lowerdata in data-only layers

 Documentation/filesystems/overlayfs.rst |  32 +++++++
 fs/overlayfs/copy_up.c                  |   9 ++
 fs/overlayfs/export.c                   |   2 +-
 fs/overlayfs/file.c                     |  21 +++-
 fs/overlayfs/inode.c                    |  18 +++-
 fs/overlayfs/namei.c                    | 121 +++++++++++++++++++++++-
 fs/overlayfs/overlayfs.h                |   2 +
 fs/overlayfs/ovl_entry.h                |  11 ++-
 fs/overlayfs/super.c                    |  68 +++++++++----
 fs/overlayfs/util.c                     |  33 ++++++-
 10 files changed, 286 insertions(+), 31 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-04-12 13:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 13:54 Amir Goldstein [this message]
2023-04-12 13:54 ` [PATCH 1/5] ovl: remove unneeded goto instructions Amir Goldstein
2023-04-18 11:37   ` Alexander Larsson
2023-04-12 13:54 ` [PATCH 2/5] ovl: introduce data-only lower layers Amir Goldstein
2023-04-18 12:02   ` Alexander Larsson
2023-04-18 13:33     ` Amir Goldstein
2023-04-18 14:20       ` Alexander Larsson
2023-04-18 15:29         ` Amir Goldstein
2023-04-12 13:54 ` [PATCH 3/5] ovl: implement lookup in data-only layers Amir Goldstein
2023-04-18 12:40   ` Alexander Larsson
2023-04-18 13:41     ` Amir Goldstein
2023-04-18 14:00       ` Alexander Larsson
2023-04-18 14:07         ` Amir Goldstein
2023-04-12 13:54 ` [PATCH 4/5] ovl: prepare for lazy lookup of lowerdata inode Amir Goldstein
2023-04-18 12:53   ` Alexander Larsson
2023-04-26 14:56   ` Miklos Szeredi
2023-04-27 11:12     ` Amir Goldstein
2023-04-27 11:43       ` Amir Goldstein
2023-04-12 13:54 ` [PATCH 5/5] ovl: implement lazy lookup of lowerdata in data-only layers Amir Goldstein
2023-04-18 13:06   ` Alexander Larsson

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=20230412135412.1684197-1-amir73il@gmail.com \
    --to=amir73il@gmail.com \
    --cc=alexl@redhat.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