From: Dave Chinner <david@fromorbit.com>
To: Xiong Zhou <xzhou@redhat.com>
Cc: amir73il@gmail.com, fstests@vger.kernel.org, miklos@szeredi.hu,
jack@suse.cz
Subject: Re: [PATCH v4] generic: add stress test for fanotify and inotify
Date: Mon, 12 Feb 2018 18:02:55 +1100 [thread overview]
Message-ID: <20180212070255.GD7000@dastard> (raw)
In-Reply-To: <1518414408-23149-1-git-send-email-xzhou@redhat.com>
On Mon, Feb 12, 2018 at 01:46:48PM +0800, 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
Nice and concise!
Thanks for updating the fix reference.
-Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2018-02-12 7:03 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 [this message]
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
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=20180212070255.GD7000@dastard \
--to=david@fromorbit.com \
--cc=amir73il@gmail.com \
--cc=fstests@vger.kernel.org \
--cc=jack@suse.cz \
--cc=miklos@szeredi.hu \
--cc=xzhou@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
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.