All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	linux-unionfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH 5/5] overlay: test mount error cases with exclusive directories
Date: Wed, 12 Jul 2017 18:47:42 +0800	[thread overview]
Message-ID: <20170712104741.GD7015@eguan.usersys.redhat.com> (raw)
In-Reply-To: <1499802726-11045-6-git-send-email-amir73il@gmail.com>

On Tue, Jul 11, 2017 at 10:52:06PM +0300, Amir Goldstein wrote:
> Expect EBUSY when trying to mount overlay when:
> - Upper dir is in-use by another overlay mount
> - Work dir is in-use by another overlay mount
> 
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>

>From patch 2/5, seems this behavior requires inode index feature to be
enabled, and now test fails on old kernels for me. Is this expected?

Thanks,
Eryu

  reply	other threads:[~2017-07-12 10:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-11 19:52 [PATCH 0/5] overlay mount tests Amir Goldstein
2017-07-11 19:52 ` [PATCH 1/5] overlay/014: remove unneeded require and include Amir Goldstein
2017-07-11 19:52 ` [PATCH 2/5] overlay/014: fix test with inodes index enabled Amir Goldstein
2017-07-12 10:36   ` Eryu Guan
2017-07-12 10:45     ` Amir Goldstein
2017-07-11 19:52 ` [PATCH 3/5] overlay: create overlay/mount test group Amir Goldstein
2017-07-11 19:52 ` [PATCH 4/5] overlay: test cases that force read-only mount Amir Goldstein
2017-07-12 10:31   ` Eryu Guan
2017-07-12 10:37     ` Amir Goldstein
2017-07-11 19:52 ` [PATCH 5/5] overlay: test mount error cases with exclusive directories Amir Goldstein
2017-07-12 10:47   ` Eryu Guan [this message]
2017-07-12 11:08     ` Amir Goldstein
2017-07-12 11:46       ` Eryu Guan
2017-07-12 11:53         ` Amir Goldstein
2017-07-12 12:07   ` [PATCH v2 " 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=20170712104741.GD7015@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=amir73il@gmail.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.