All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Chandan Rajendra <chandan@linux.vnet.ibm.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>, zhangyi <yi.zhang@huawei.com>,
	"linux-unionfs@vger.kernel.org" <linux-unionfs@vger.kernel.org>
Subject: Re: [PATCH v5 2/4] ovl: allocate anonymous devs for lowerdirs
Date: Wed, 1 Nov 2017 15:34:38 +0200	[thread overview]
Message-ID: <CAOQ4uxj=dLaikbukL0pEwoTQ9oFS0Y0d1ZQ+3Mt0fsxCdw1SPg@mail.gmail.com> (raw)
In-Reply-To: <1609807.jvdsPgIkQ8@localhost.localdomain>

On Wed, Nov 1, 2017 at 3:17 PM, Chandan Rajendra
<chandan@linux.vnet.ibm.com> wrote:
> On Wednesday, November 1, 2017 4:31:00 AM IST Amir Goldstein wrote:
...
>>
>> Pushed the requested changes to branch:
>> https://github.com/amir73il/linux/commits/ovl-nonsamefs-v6
>>
>> Currently same tip as overlayfs-devel.
>>
>
> Amir, The changes look fine to me. Thanks for addressing the review comments.
>

No problem, but just found another problem in testing -
When we iterate pure lower or upper dir type entries
we do not adjust their d_ino to overlay ino, which is differnt
than real ino for non-samefs dirs.
example ((mnt/b is pure upper):
=====================================
# ls -li /mnt/
total 0
16237 drwxr-xr-x  2 root root   40 Nov  1 13:12 b

# find /mnt -inum 16237
/mnt/b

# ../xfstests/src/t_dir_type /mnt/b 16237
. d

# ../xfstests/src/t_dir_type /mnt/b 16237

<nothing>
=====================================

This problem does not affect 'find -inum' because 'find' always
does stat(2) for directories to check st_ino and more.

But the problem does affect decoding of NFS file handles
because the default get_name() implementation relies on
d_ino lookup to match child name with disconnected child dentry.

I will fix it up.

Chandan,

When you have time, please send a fix to xfstests 038 and 041 to test
this missed use case and please send a nonsamefs test variant of 017.

Thanks,
Amir.

  reply	other threads:[~2017-11-01 13:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30 20:27 [PATCH v5 0/4] Overlayfs: constant st_ino/d_ino for non-samefs Amir Goldstein
2017-10-30 20:27 ` [PATCH v5 1/4] ovl: move include of ovl_entry.h into overlayfs.h Amir Goldstein
2017-10-31 13:14   ` Miklos Szeredi
2017-10-31 13:22     ` Amir Goldstein
2017-10-30 20:27 ` [PATCH v5 2/4] ovl: allocate anonymous devs for lowerdirs Amir Goldstein
2017-10-31 13:43   ` Miklos Szeredi
2017-10-31 13:53     ` Amir Goldstein
2017-10-31 23:01       ` Amir Goldstein
2017-11-01 13:17         ` Chandan Rajendra
2017-11-01 13:34           ` Amir Goldstein [this message]
2017-11-01 14:42   ` Vivek Goyal
2017-11-01 15:02     ` Amir Goldstein
2017-11-01 15:47       ` Vivek Goyal
2017-11-01 16:41         ` Amir Goldstein
2017-11-02 12:27           ` Vivek Goyal
2017-11-02 12:47             ` Amir Goldstein
2017-11-02 14:05               ` Vivek Goyal
2017-11-02 14:38                 ` Amir Goldstein
2017-11-01 15:41   ` Vivek Goyal
2017-11-01 16:30     ` Amir Goldstein
2017-10-30 20:27 ` [PATCH v5 3/4] ovl: relax same fs constrain for constant st_ino Amir Goldstein
2017-10-30 20:27 ` [PATCH v5 4/4] ovl: relax same fs constraint for constant d_ino 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='CAOQ4uxj=dLaikbukL0pEwoTQ9oFS0Y0d1ZQ+3Mt0fsxCdw1SPg@mail.gmail.com' \
    --to=amir73il@gmail.com \
    --cc=chandan@linux.vnet.ibm.com \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=yi.zhang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.