All of lore.kernel.org
 help / color / mirror / Atom feed
From: Murphy Zhou <jencce.kernel@gmail.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v2] kernel/fs/fsnotify-stress: fsnotify stress test
Date: Fri, 4 Mar 2022 11:28:37 +0800	[thread overview]
Message-ID: <CADJHv_sUgK0FBZh7w_n03CZnL-+bNcXGn7DP1seJCa5qBWutwQ@mail.gmail.com> (raw)
In-Reply-To: <YiDdRhIdh12/23HM@pevik>

Hi Petr,

On Thu, Mar 3, 2022 at 11:22 PM Petr Vorel <pvorel@suse.cz> wrote:
>
> > This is a stress tests that exercises fanotify and inotify interfaces
> > while IO going on. It ignores some failures of syscalls to let the
> > stress go on. If the kernel does not panic or hang after a certain
> > period of time of testing, test pass.
>
> > Signed-off-by: Murphy Zhou <jencce.kernel@gmail.com>
> > ---
> > v2:
> >       Merge all into one C programme.
> >       Changed dirname of the testcase.
> >       Run fs_racer.sh from this.
> Also tests in testcases/kernel/fs/racer/ are very old scripts with questionable
> code quality. I would not use them with new tests.  Not sure whether these tests
> are useful at all, but if yes they please take the idea and implement it in new
> C API, so that they can be called by forked thread.

Fair enough. I'll test to see if this part is necessary.

Thanks!

>
> Why C? Running shell test from C is probably not acceptable. We have enough
> problems with shell tests which use C binaries. Doing it vice versa can bring
> even more problems.
>
> fs_racer.sh runs many times fs_racer_file_create.sh, which mainly does:
> dd if=/dev/zero of=$DIR/$file bs=1k count=$SIZE
>
> => nothing hard to implement in C.
>
> Kind regards,
> Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-03-04  3:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25  2:47 [LTP] [PATCH 1/2] kernel/fs/fs-notify: fsnotify stress tests Murphy Zhou
2022-01-25  7:29 ` Amir Goldstein
2022-01-25  8:30   ` Murphy Zhou
2022-01-25 10:28     ` Petr Vorel
2022-01-25 10:56     ` Cyril Hrubis
2022-01-25 11:04 ` Cyril Hrubis
2022-01-27  4:42   ` Murphy Zhou
2022-02-28  6:29   ` Murphy Zhou
2022-02-28  6:42     ` Petr Vorel
2022-03-03  3:06       ` [LTP] [PATCH v2] kernel/fs/fsnotify-stress: fsnotify stress test Murphy Zhou
2022-03-03 15:22         ` Petr Vorel
2022-03-04  3:28           ` Murphy Zhou [this message]
2022-03-08  1:38           ` [LTP] [PATCH v3] " Murphy Zhou
2022-03-09 10:38             ` Cyril Hrubis
2022-03-10 20:48               ` Petr Vorel
2022-09-02  7:58                 ` Murphy Zhou
2022-09-02  8:17                 ` [LTP] [PATCH v4] " Murphy Zhou
2022-10-17  9:40                   ` 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=CADJHv_sUgK0FBZh7w_n03CZnL-+bNcXGn7DP1seJCa5qBWutwQ@mail.gmail.com \
    --to=jencce.kernel@gmail.com \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    /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.