public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscalls/fanotify: new test for mount ignore mask
Date: Thu, 13 Sep 2018 13:45:32 +0200	[thread overview]
Message-ID: <20180913114531.GA3030@rei.lan> (raw)
In-Reply-To: <CAOQ4uxho8Fh7=eJr962UeTr4dwqnOjFQJZxvJ4ZreMa_MRJDfQ@mail.gmail.com>

Hi!
> All right. I have already written this test with a test index to cover
> all possible
> mixes of mark types include and exclude masks:
> https://github.com/amir73il/ltp/blob/fanotify_sb/testcases/kernel/syscalls/fanotify/fanotify13.c
> This gives better coverage than fanotify06 and fanotify10 combined.
> 
> However, if I modify test fanotify06 instead of forking test fanotify10, the
> test (fanotify06) is going to start failing on non-master kernels.
> Is that acceptable for LTP? I am asking because in fstests project, we have
> the practice not to change an existing test to failing. When we find a
> new regression we write a new variant of the test for it.

We do not have a rule lik this but it sounds like a reasonable rule to
me, since when existing test starts to fail it does look like a
regression in the tests itself.

> If changing an existing test to cover more cases is appropriate than I am
> going to generalize fanotify06 (as fanotify13 linked above) and then
> when FAN_MARK_FILESYSTEM mark type support is added to kernel
> all I will need to do is change the test again to add another mark type
> to  fanotify_mark_types array.

I guess that either would be fine. In the end someone has to look
closely at failing tests anyway to say what exactly happened.

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2018-09-13 11:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-08 14:24 [LTP] [PATCH] syscalls/fanotify: misc cleanups Amir Goldstein
2018-09-08 14:24 ` [LTP] [PATCH] syscalls/fanotify: new test for mount ignore mask Amir Goldstein
2018-09-11  9:07   ` Richard Palethorpe
2018-09-11 14:32     ` Amir Goldstein
2018-09-13 11:45       ` Cyril Hrubis [this message]
2018-09-13 12:19         ` Amir Goldstein
2018-09-13 13:12           ` Richard Palethorpe
2018-09-10 14:35 ` [LTP] [PATCH] syscalls/fanotify: misc cleanups Richard Palethorpe
2018-09-10 18:20   ` Amir Goldstein
2018-09-11  7:51     ` Richard Palethorpe

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=20180913114531.GA3030@rei.lan \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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