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/7] Prepare for lazy lowerdata lookup
Date: Sat,  8 Apr 2023 19:42:55 +0300	[thread overview]
Message-ID: <20230408164302.1392694-1-amir73il@gmail.com> (raw)

Miklos,

This series is a cleanup towards the lazy lowerdata lookup patches that
I mentioned in an earlier email [1].  The lazy lowerdata patches are
ready including tests, but I am waiting for your feedback on the
data-only layers before I post the complete series.

I am posting this cleanup series independently, because it mostly [*]
stands on its own.

Specifically, patch #1 is a bug fix for stable.

Feel free to take just patch #1, or only part of the cleanup or wait for
the posting of the complete work.

Thanks,
Amir.

[*] The last patch, which reserves the space for lowerdata_redirect is
not completely independent of the lazy lowerdata series, but I preferred
to do it this way then to remove the lowerdata inode union field and add
lowerdata_redirect later, because I think the change is easier to review
this way.

[1] https://lore.kernel.org/linux-unionfs/CAOQ4uxich227fP7bGSCNqx-JX5h36O-MLwqPoy0r33tuH=z2cA@mail.gmail.com/

Amir Goldstein (7):
  ovl: update of dentry revalidate flags after copy up
  ovl: use OVL_E() and OVL_E_FLAGS() accessors
  ovl: use ovl_numlower() and ovl_lowerstack() accessors
  ovl: factor out ovl_free_entry() and ovl_stack_*() helpers
  ovl: move ovl_entry into ovl_inode
  ovl: deduplicate lowerpath and lowerstack[0]
  ovl: replace lowerdata inode reference with lowerdata redirect

 fs/overlayfs/copy_up.c   |   2 +
 fs/overlayfs/dir.c       |   5 +-
 fs/overlayfs/export.c    |  37 ++++-----
 fs/overlayfs/inode.c     |  20 ++---
 fs/overlayfs/namei.c     |  75 +++++++++---------
 fs/overlayfs/overlayfs.h |  24 ++++--
 fs/overlayfs/ovl_entry.h |  63 +++++++++++----
 fs/overlayfs/super.c     |  86 +++++++-------------
 fs/overlayfs/util.c      | 164 +++++++++++++++++++++++++++++----------
 9 files changed, 281 insertions(+), 195 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-04-08 16:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-08 16:42 Amir Goldstein [this message]
2023-04-08 16:42 ` [PATCH 1/7] ovl: update of dentry revalidate flags after copy up Amir Goldstein
2023-04-14  7:21   ` Gao Xiang
2023-04-27  5:48     ` Amir Goldstein
2023-04-27  6:11       ` Gao Xiang
2023-04-08 16:42 ` [PATCH 2/7] ovl: use OVL_E() and OVL_E_FLAGS() accessors Amir Goldstein
2023-04-17 14:20   ` Alexander Larsson
2023-04-08 16:42 ` [PATCH 3/7] ovl: use ovl_numlower() and ovl_lowerstack() accessors Amir Goldstein
2023-04-17 14:38   ` Alexander Larsson
2023-04-08 16:42 ` [PATCH 4/7] ovl: factor out ovl_free_entry() and ovl_stack_*() helpers Amir Goldstein
2023-04-17 15:00   ` Alexander Larsson
2023-04-08 16:43 ` [PATCH 5/7] ovl: move ovl_entry into ovl_inode Amir Goldstein
2023-04-18  7:55   ` Alexander Larsson
2023-04-27  6:07     ` Amir Goldstein
2023-04-08 16:43 ` [PATCH 6/7] ovl: deduplicate lowerpath and lowerstack[0] Amir Goldstein
2023-04-18  8:10   ` Alexander Larsson
2023-04-27  6:29     ` Amir Goldstein
2023-04-26 12:07   ` Miklos Szeredi
2023-04-27  6:27     ` Amir Goldstein
2023-04-08 16:43 ` [PATCH 7/7] ovl: replace lowerdata inode reference with lowerdata redirect Amir Goldstein
2023-04-18  8:19   ` Alexander Larsson
2023-04-26 12:38   ` Miklos Szeredi
2023-04-27  6:32     ` 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=20230408164302.1392694-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