All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <guaneryu@gmail.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	"Darrick J . Wong" <darrick.wong@oracle.com>,
	overlayfs <linux-unionfs@vger.kernel.org>,
	fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH] overlay/061: remove from auto and quick groups
Date: Sun, 23 Jun 2019 21:25:03 +0800	[thread overview]
Message-ID: <20190623132503.GM15846@desktop> (raw)
In-Reply-To: <CAOQ4uxiDZjr2+EyjWtimjLxFHrMN13K4N5Aw+9BACPmx+2W6Kg@mail.gmail.com>

On Wed, Jun 19, 2019 at 01:47:01PM +0300, Amir Goldstein wrote:
> >
> > I did not observe any regressing with check -overlay -g generic/quick
> > compared to check -g generic/quick on xfs with recent kernel.
> > I did not test all filesystems and -g generic/auto with recent kernel,
> > but I am not aware of any expected failures specific for -overlay run
> > on generic tests.
> >
> 
> Oh! I was lying. I *did* notice two regressions with
> check -overlay -g generic/quick (compared to xfs),
> so I posted fixes for them:
> 
> 1) generic/504 is failing with -overlay on master.
> 
> This kernel fix commit is on linux-next:
> 6ef048fd5955 locks: eliminate false positive conflicts for write lease
> 
> 2) generic/555 (was just merged this week) is failing with
> -overlay on master.
> 
> This kernel fix commit is on Miklos' overlayfs-next:
> 941d935ac763 ovl: fix wrong flags check in FS_IOC_FS[SG]ETXATTR ioctls

Thanks a lot for the detailed information!

Eryu

      reply	other threads:[~2019-06-23 13:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-18  6:43 [PATCH] overlay/061: remove from auto and quick groups Amir Goldstein
2019-06-19 10:47 ` Amir Goldstein
2019-06-23 13:25   ` Eryu Guan [this message]

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=20190623132503.GM15846@desktop \
    --to=guaneryu@gmail.com \
    --cc=amir73il@gmail.com \
    --cc=darrick.wong@oracle.com \
    --cc=fstests@vger.kernel.org \
    --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 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.