linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: overlayfs <linux-unionfs@vger.kernel.org>,
	Eryu Guan <guaneryu@gmail.com>
Subject: Re: [PATCH] ovl: skip stale entries in merge dir cache iteration
Date: Mon, 19 Jul 2021 19:43:22 +0300	[thread overview]
Message-ID: <CAOQ4uxjeHfEy-NHQ3s8gX6Rge9xUkJhfGWGNBFSRj6t4mhAUMQ@mail.gmail.com> (raw)
In-Reply-To: <CAJfpegtZq=EPuoU_wxr4yEJtime4vW6oPFBnX5whrXS3ZSA6oQ@mail.gmail.com>

On Mon, Jul 19, 2021 at 6:24 PM Miklos Szeredi <miklos@szeredi.hu> wrote:
>
> On Fri, 4 Jun 2021 at 12:43, Amir Goldstein <amir73il@gmail.com> wrote:
> >
> > On Mon, Apr 26, 2021 at 6:20 PM Amir Goldstein <amir73il@gmail.com> wrote:
> > >
> > > On the first getdents call, ovl_iterate() populates the readdir cache
> > > with a list of entries, but for upper entries with origin lower inode,
> > > p->ino remains zero.
> > >
> > > Following getdents calls traverse the readdir cache list and call
> > > ovl_cache_update_ino() for entries with zero p->ino to lookup the entry
> > > in the overlay and return d_ino that is consistent with st_ino.
> > >
> > > If the upper file was unlinked between the first getdents call and the
> > > getdents call that lists the file entry, ovl_cache_update_ino() will not
> > > find the entry and fall back to setting d_ino to the upper real st_ino,
> > > which is inconsistent with how this object was presented to users.
> > >
> > > Instead of listing a stale entry with inconsistent d_ino, simply skip
> > > the stale entry, which is better for users.
> > >
> >
> > Miklos,
> >
> > I forgot to follow up on this patch.
> > Upstream xfstest overlay/077 is failing without this patch.
>
> Can't reproduce (on ext4/xfs and "-oxino=on").
>
> Is there some trick?

Not sure. overlay/077 fails for me on v5.14.0-rc2 on ext4/xfs.

     QA output created by 077
    +entry m100 has inconsistent d_ino (234 != 232)
    +entry f100 has inconsistent d_ino (335 != 16777542)
     Silence is golden

Maybe you need to build src/t_dir_offset2?

Thanks,
Amir.

  reply	other threads:[~2021-07-19 17:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26 15:20 [PATCH] ovl: skip stale entries in merge dir cache iteration Amir Goldstein
2021-06-04 10:43 ` Amir Goldstein
2021-07-19 15:24   ` Miklos Szeredi
2021-07-19 16:43     ` Amir Goldstein [this message]
2021-07-20  4:19       ` Miklos Szeredi
2021-07-20  4:22         ` Miklos Szeredi
2021-07-20  7:18           ` Amir Goldstein
2021-07-20 14:55             ` Amir Goldstein
2021-07-20 16:17               ` Amir Goldstein
2021-07-21 13:08                 ` 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=CAOQ4uxjeHfEy-NHQ3s8gX6Rge9xUkJhfGWGNBFSRj6t4mhAUMQ@mail.gmail.com \
    --to=amir73il@gmail.com \
    --cc=guaneryu@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;
as well as URLs for NNTP newsgroup(s).