All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiong Zhou <xzhou@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: Xiong Zhou <xzhou@redhat.com>,
	amir73il@gmail.com, fstests@vger.kernel.org, miklos@szeredi.hu,
	david@fromorbit.com
Subject: Re: [PATCH v4] generic: add stress test for fanotify and inotify
Date: Fri, 16 Feb 2018 08:38:23 +0800	[thread overview]
Message-ID: <20180216003823.tzsjpmhsu42mj3tu@XZHOUW.usersys.redhat.com> (raw)
In-Reply-To: <20180215092343.od4to3x7loklzqu6@quack2.suse.cz>

On Thu, Feb 15, 2018 at 10:23:43AM +0100, Jan Kara wrote:
> On Thu 15-02-18 08:49:40, Xiong Zhou wrote:
> > On Wed, Feb 14, 2018 at 12:03:31PM +0100, Jan Kara wrote:
> > > On Mon 12-02-18 13:46:48, Xiong Zhou wrote:
> > > > Stress test for fanotify and inotify. Exercise fanotify and
> > > > inotify user interfaces in loop while other stress tests going
> > > > on in the watched test directory.
> > > > 
> > > > Watching slab object inotify_inode_mark size, report fail
> > > > it increases too fast. This may lead to a crash if OOM killer
> > > > invoked.
> > > > 
> > > > kernel commit related to the fixes in v4.15-rc1:
> > > > 0d6ec07 fsnotify: pin both inode and vfsmount mark
> > > > 
> > > > Signed-off-by: Xiong Zhou <xzhou@redhat.com>
> > > 
> > > I'm sorry for chiming in so late but I was on vacation. Just one question:
> > > Currently, all inotify and fanotify tests are part of LTP. Is there any
> > > good reason for putting this particular test to fstests and not LTP?
> > 
> > It's handy to test with bash and c. fstests is more convenient to do that.
> 
> Hum, I don't understand. You can just run the executables created by LTP.

Like *_files functions and run fsstress in this patch. It's doable by c,
just with more code.

Thanks,
Xiong

> E.g.:
> 
> jack@quack2:~/source/ltp> testcases/kernel/syscalls/inotify/inotify01 
> inotify01    1  TPASS  :  get event: wd=1 mask=4 cookie=0 len=0
> inotify01    2  TPASS  :  get event: wd=1 mask=20 cookie=0 len=0
> inotify01    3  TPASS  :  get event: wd=1 mask=1 cookie=0 len=0
> inotify01    4  TPASS  :  get event: wd=1 mask=10 cookie=0 len=0
> inotify01    5  TPASS  :  get event: wd=1 mask=20 cookie=0 len=0
> inotify01    6  TPASS  :  get event: wd=1 mask=2 cookie=0 len=0
> inotify01    7  TPASS  :  get event: wd=1 mask=8 cookie=0 len=0
> jack@quack2:~/source/ltp>
> 
> I don't see anything less handy than in fstests. I do agree that LTP is huge
> so the initial step of downloading it and compiling takes longer than for
> fstests but that's about it.
> 
> 								Honza
> -- 
> Jan Kara <jack@suse.com>
> SUSE Labs, CR

  reply	other threads:[~2018-02-16  0:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CCAOQ4uxh2ZmEJi8gbiDRsYefV+XC20TNLjW9OFOZM0=j0_0yf+Q@mail.gmail.com>
2018-02-11  6:59 ` [PATCH v3] generic: add stress test for fanotify and inotify Xiong Zhou
2018-02-11 20:03   ` Amir Goldstein
2018-02-12  0:41     ` Xiong Zhou
2018-02-12  3:50       ` Amir Goldstein
2018-02-12  4:33         ` Xiong Zhou
2018-02-12  5:08           ` Dave Chinner
2018-02-12  5:38             ` Xiong Zhou
2018-02-12  5:46               ` [PATCH v4] " Xiong Zhou
2018-02-12  7:02                 ` Dave Chinner
2018-02-12  8:34                   ` Xiong Zhou
2018-02-14 11:03                 ` Jan Kara
2018-02-14 11:22                   ` Amir Goldstein
2018-02-14 15:03                     ` Eryu Guan
2018-02-15  8:33                       ` Amir Goldstein
2018-02-15  0:49                   ` Xiong Zhou
2018-02-15  9:23                     ` Jan Kara
2018-02-16  0:38                       ` Xiong Zhou [this message]
2018-02-16  9:52                         ` Jan Kara
2018-02-17  1:21                           ` Xiong Zhou
2018-02-12  5:17           ` [PATCH v3] " Xiong Zhou
2018-02-12  6:48             ` 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=20180216003823.tzsjpmhsu42mj3tu@XZHOUW.usersys.redhat.com \
    --to=xzhou@redhat.com \
    --cc=amir73il@gmail.com \
    --cc=david@fromorbit.com \
    --cc=fstests@vger.kernel.org \
    --cc=jack@suse.cz \
    --cc=miklos@szeredi.hu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.