linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Yurkov, Vyacheslav" <Vyacheslav.Yurkov@bruker.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Vyacheslav Yurkov <uvv.mail@gmail.com>,
	Miklos Szeredi <miklos@szeredi.hu>,
	overlayfs <linux-unionfs@vger.kernel.org>
Subject: RE: [PATCH v3 3/3] ovl: do not set overlay.opaque for new directories
Date: Fri, 4 Jun 2021 14:50:52 +0000	[thread overview]
Message-ID: <AM8PR10MB416123A0AAE3135A15C72FF7863B9@AM8PR10MB4161.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAOQ4uxiAkMYiTQEg8A61tUU4jGCs9YSCVYuttGiQobif6rhmjA@mail.gmail.com>

You were a bit faster than me 😊
I was able to extend my system to provide all needed utilities / kernel features and also got all the tests run.

But to not loose my progress, I'd like to contribute my yocto recipe to the meta-openembedded project. It would be great if you could clarify a few things for me.

1) The base test harness is xfstests, URL: git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
2) Ovelayfs testsuite, URL: https://github.com/amir73il/unionmount-testsuite.git
3) The test suite also requires fsck.overlay, URL: https://github.com/hisilicon/overlayfs-progs

Are all the URLs are correct?
#2 and #3 are official repositories so to say?

Thanks,
Vyacheslav


- confidential -

> -----Original Message-----
> From: Amir Goldstein <amir73il@gmail.com>
> Sent: Friday, June 4, 2021 14:33
> To: Yurkov, Vyacheslav <Vyacheslav.Yurkov@bruker.com>
> Cc: Vyacheslav Yurkov <uvv.mail@gmail.com>; Miklos Szeredi
> <miklos@szeredi.hu>; overlayfs <linux-unionfs@vger.kernel.org>
> Subject: Re: [PATCH v3 3/3] ovl: do not set overlay.opaque for new
> directories
> 
> > Ok we still need to verify no regressions on those skipped test.
> > I can run them on my setup when I get the time if you cannot find
> > another test setup which meets the requirements.
> >
> 
> Run the overlay/quick tests on your patches.
> No regressions.
> 
> Thanks,
> Amir.

  reply	other threads:[~2021-06-04 14:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27 17:45 [PATCH v3 1/3] ovl: disable decoding null uuid with redirect dir Vyacheslav Yurkov
2021-05-27 17:45 ` [PATCH v3 2/3] ovl: add ovl_allow_offline_changes() helper Vyacheslav Yurkov
2021-05-27 17:45 ` [PATCH v3 3/3] ovl: do not set overlay.opaque for new directories Vyacheslav Yurkov
2021-05-28 11:38   ` Amir Goldstein
2021-06-01  6:53     ` Yurkov, Vyacheslav
2021-06-01  8:33       ` Amir Goldstein
2021-06-01 16:29         ` Yurkov, Vyacheslav
2021-06-01 18:29           ` Amir Goldstein
2021-06-04 12:32             ` Amir Goldstein
2021-06-04 14:50               ` Yurkov, Vyacheslav [this message]
2021-06-04 19:18                 ` Amir Goldstein
2021-07-19 14:29   ` 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=AM8PR10MB416123A0AAE3135A15C72FF7863B9@AM8PR10MB4161.EURPRD10.PROD.OUTLOOK.COM \
    --to=vyacheslav.yurkov@bruker.com \
    --cc=amir73il@gmail.com \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=uvv.mail@gmail.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
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).