public inbox for linux-unionfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: amir73il@gmail.com, miklos@szeredi.hu
Cc: linux-unionfs@vger.kernel.org, yangerkun@huawei.com, vgoyal@redhat.com
Subject: [PATCH v2 0/3] overlayfs: Do not check metacopy in ovl_get_inode()
Date: Mon,  1 Jun 2020 11:56:49 -0400	[thread overview]
Message-ID: <20200601155652.17486-1-vgoyal@redhat.com> (raw)

Hi,

This is V2 of the patches. Took care of few suggestions from Amir.

This series tries to implement Amir's suggestion of initializing
OVL_UPPERDATA in callers of ovl_get_inode() and move checking of 
metacopy xattr out of ovl_get_inode().

It also has to patches to cleanup metacopy logic a bit and make it
little more readable and understandable in ovl_lookup().

yangerkun, can you please make sure if this patch series fixes the
xfstest issue you were facing once in a while.

Vivek Goyal (3):
  overlayfs: Simplify setting of origin for index lookup
  overlayfs: ovl_lookup(): Use only uppermetacopy state
  overlayfs: Initialize OVL_UPPERDATA in ovl_lookup()

 fs/overlayfs/dir.c   |  2 +
 fs/overlayfs/inode.c | 11 +-----
 fs/overlayfs/namei.c | 89 ++++++++++++++++++++++++--------------------
 3 files changed, 51 insertions(+), 51 deletions(-)

-- 
2.25.4


             reply	other threads:[~2020-06-01 15:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01 15:56 Vivek Goyal [this message]
2020-06-01 15:56 ` [PATCH v2 1/3] overlayfs: Simplify setting of origin for index lookup Vivek Goyal
2020-06-01 15:56 ` [PATCH v2 2/3] overlayfs: ovl_lookup(): Use only uppermetacopy state Vivek Goyal
2020-06-01 16:25   ` Amir Goldstein
2020-06-01 15:56 ` [PATCH v2 3/3] overlayfs: Initialize OVL_UPPERDATA in ovl_lookup() Vivek Goyal
2020-06-03  7:13 ` [PATCH v2 0/3] overlayfs: Do not check metacopy in ovl_get_inode() yangerkun
2020-06-03  7:59   ` Miklos Szeredi

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=20200601155652.17486-1-vgoyal@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=amir73il@gmail.com \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=yangerkun@huawei.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