linux-unionfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Eryu Guan <eguan@linux.alibaba.com>
Cc: Eryu Guan <guan@eryu.me>, Eryu Guan <guaneryu@gmail.com>,
	Icenowy Zheng <icenowy@aosc.io>,
	Chengguang Xu <cgxu519@mykernel.net>,
	Xiao Yang <yangx.jy@cn.fujitsu.com>,
	Miklos Szeredi <miklos@szeredi.hu>,
	overlayfs <linux-unionfs@vger.kernel.org>,
	fstests <fstests@vger.kernel.org>
Subject: Re: [PATCH 3/4] src/t_immutable: Allow setting flags on existing files
Date: Mon, 25 Jan 2021 15:17:22 +0200	[thread overview]
Message-ID: <CAOQ4uxgkdtd-Bh-y2urrXSQ6OVYe=ZgiUiELQwYsMPuroPiU8g@mail.gmail.com> (raw)
In-Reply-To: <20210125124629.GF58500@e18g06458.et15sqa>

On Mon, Jan 25, 2021 at 2:46 PM Eryu Guan <eguan@linux.alibaba.com> wrote:
>
> On Sun, Jan 24, 2021 at 05:32:15PM +0200, Amir Goldstein wrote:
> > On Sun, Jan 24, 2021 at 5:14 PM Eryu Guan <guan@eryu.me> wrote:
> > >
> [snap]
> > > >
> > > >       if (create) {
> > > >         ret = create_test_area(argv[argc-1]);
> > > > -       if (ret || !runtest) {
> > > > +       if (ret || allow_existing) {
> > >
> > > With this change, compiler warns about 'runtest' is set but not used,
> > > and 'allow_existing' now indicates '!runtest' implicitly, which seems
> > > subtle. I think it's better to keep 'runtest' as the indicator to
> > > actually run the test?
> > >
> >
> > Sure, I removed it by mistake.
>
> Then this is the only place that needs update. I can fix it on commit,
> no need to resend then.
>

Excellent.

Now, about that kernel deadlock mentioned in is commented out line in
test overlay/075. The fix for that is in overlayfs-next:

147ec02b8705 - ovl: avoid deadlock on directory ioctl

But I am not so happy about adding a test that crashes stable/old kernels.
If you like I can post another test that is "dangerous" just for the deadlock
but after the fix is merged to master and 5.10.y so at least people who tests
the latest kernels will not crash.

Let me know your preference.

Thanks,
Amir.

  reply	other threads:[~2021-01-25 13:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-16 16:56 [PATCH 0/4] Tests for overlayfs immutable/append-only files Amir Goldstein
2021-01-16 16:56 ` [PATCH 1/4] overlay/030: Update comment w.r.t upstream kernel Amir Goldstein
2021-01-16 16:56 ` [PATCH 2/4] src/t_immutable: factor out some helpers Amir Goldstein
2021-01-24 15:09   ` Eryu Guan
2021-01-24 15:29     ` Amir Goldstein
2021-01-25 12:35       ` Eryu Guan
2021-01-16 16:56 ` [PATCH 3/4] src/t_immutable: Allow setting flags on existing files Amir Goldstein
2021-01-24 15:14   ` Eryu Guan
2021-01-24 15:32     ` Amir Goldstein
2021-01-25 12:46       ` Eryu Guan
2021-01-25 13:17         ` Amir Goldstein [this message]
2021-01-16 16:56 ` [PATCH 4/4] overlay: Test lost immutable/append-only flags on copy-up Amir Goldstein
2021-01-25 13:24   ` Amir Goldstein
2021-01-26  8:47     ` Miklos Szeredi
2021-01-27  2:57     ` Eryu Guan
2021-01-28  6:45       ` 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='CAOQ4uxgkdtd-Bh-y2urrXSQ6OVYe=ZgiUiELQwYsMPuroPiU8g@mail.gmail.com' \
    --to=amir73il@gmail.com \
    --cc=cgxu519@mykernel.net \
    --cc=eguan@linux.alibaba.com \
    --cc=fstests@vger.kernel.org \
    --cc=guan@eryu.me \
    --cc=guaneryu@gmail.com \
    --cc=icenowy@aosc.io \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=yangx.jy@cn.fujitsu.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).