($INBOX_DIR/description missing)
 help / color / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: overlayfs <linux-unionfs@vger.kernel.org>
Cc: Vivek Goyal <vgoyal@redhat.com>, Miklos Szeredi <miklos@szeredi.hu>
Subject: Fwd: [ANNOUNCE] unionmount-testsuite: master branch updated to 509b1e7
Date: Fri, 22 Nov 2019 11:35:15 +0200
Message-ID: <CAOQ4uxiHKjNba8HD5JUWFxxJqyJxPMk3fFfA3fi-nO6uJngTAg@mail.gmail.com> (raw)
In-Reply-To: <CAOQ4uxjryJep94sLgVxV7sGab8K3yeeDUZwOYOfLtOOguW1pcA@mail.gmail.com>

Hi All,

The master branch on the unionmount-testsuite tree [1] has been updated.

Changes in this update:
- Enhance --verify with copy up state checks
- Verify metadata only copy up with --verify --meta
- Verify unified ino domain with xino requires --verify --xino

Note that this release changes xino from a test configuration that is
implied from --verify to requiring an explicit opt-in with --xino option.

This change allows more strict checking of the xino=off configuration
and exposes a kernel v4.17 regression:

 ./run --ov=1 --verify hard-link
 ...
 /mnt/a/no_foo110: File unexpectedly on upper layer

Thanks,
Amir.

[1] https://github.com/amir73il/unionmount-testsuite

The head of the master branch is commit:

1724ef2 Decouple xino configuration from --verify

New commits:

Amir Goldstein (8):
  Fix ./run --ov --verify --recycle
  Simplify initialization of __upper
  Fix instantiation of hardlinked dentry
  Record meta copy_up vs. data copy_up
  Check that files were copied up as expected
  Reset dentry copy_up state on upper layer rotate
  Check that data was not copied up with metacopy=on
  Decouple xino configuration from --verify

  reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-20 15:07 Amir Goldstein
2019-11-22  9:35 ` Amir Goldstein [this message]
2019-11-22  9:37   ` [ANNOUNCE] unionmount-testsuite: master branch updated to 1724ef2 Amir Goldstein
2020-03-18 12:33     ` [ANNOUNCE] unionmount-testsuite: master branch updated to dc24a45 Amir Goldstein
2020-04-09 18:27       ` [ANNOUNCE] unionmount-testsuite: master branch updated to a9a4f4f 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=CAOQ4uxiHKjNba8HD5JUWFxxJqyJxPMk3fFfA3fi-nO6uJngTAg@mail.gmail.com \
    --to=amir73il@gmail.com \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=vgoyal@redhat.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

($INBOX_DIR/description missing)

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-unionfs/0 linux-unionfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-unionfs linux-unionfs/ https://lore.kernel.org/linux-unionfs \
		linux-unionfs@vger.kernel.org
	public-inbox-index linux-unionfs

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-unionfs


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git