($INBOX_DIR/description missing)
 help / color / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: overlayfs <linux-unionfs@vger.kernel.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>, Vivek Goyal <vgoyal@redhat.com>
Subject: [ANNOUNCE] unionmount-testsuite: master branch updated to dc24a45
Date: Wed, 18 Mar 2020 14:33:30 +0200
Message-ID: <CAOQ4uxiKdxujdKNWBRNxtvCrq5TDJuhoW5Oede0Hu1myoKfeEQ@mail.gmail.com> (raw)
In-Reply-To: <CAOQ4uxhBBnr5zFOn1Dr-XtDSo=p3BovyhK6xZh22GA=dv1L8Bw@mail.gmail.com>

Hi All,

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

Changes in this update:
- Align with v5.6-rc1 overlayfs code

The previous release of unionmount-testsuite (1724ef2) exposed a kernel
v4.17 regression:

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

This kernel regression was fixed in v5.6-rc1 by commit  b7bf9908e17c
("ovl: fix corner case of non-constant st_dev;st_ino").
This release of unionmount-testsuite adapts the layer checks to the fixed
logic of v5.6-rc1.

The regression test above still fails on kernel v5.5, but with a
different error:
 ./run --ov=1 --verify hard-link
 ...
 /mnt/a/no_foo110: inode number/layer changed on copy up (got
34:434190, was 34:430077)


Thanks,
Amir.

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

The head of the master branch is commit:

dc24a45 Update layer check with pseudo st_dev for upper layer

New commits:

Amir Goldstein (1):
  Update layer check with pseudo st_dev for upper layer

      reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-20 15:07 [ANNOUNCE] unionmount-testsuite: master branch updated to 509b1e7 Amir Goldstein
2019-11-22  9:35 ` Fwd: " Amir Goldstein
2019-11-22  9:37   ` [ANNOUNCE] unionmount-testsuite: master branch updated to 1724ef2 Amir Goldstein
2020-03-18 12:33     ` Amir Goldstein [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=CAOQ4uxiKdxujdKNWBRNxtvCrq5TDJuhoW5Oede0Hu1myoKfeEQ@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