All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: zhaogongyi <zhaogongyi@huawei.com>
Cc: Matthew Bobrowski <repnop@google.com>,
	"ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v3] syscalls/fanotify07: Add stop_children() to cleanup()
Date: Tue, 23 Nov 2021 09:12:13 +0100	[thread overview]
Message-ID: <YZyiXbx5QOymJSsE@pevik> (raw)
In-Reply-To: <e58da01199ac4995805b2053f5e44a56@huawei.com>

Hi all,

> Hi,

> I have test the patch through setting "ulimit -n 20" and while true;do ./fanotify07 &;echo "";done 

> Or just add a tst_brk as follow:

>         /*
>          * Create and destroy another instance. This may hang if
>          * unanswered fanotify events block notification subsystem.
>          */
>         newfd = setup_instance();

>         SAFE_CLOSE(newfd);

> 		/* inject */
> 		tst_brk(TBROK, "exit abnormally");

>         tst_res(TPASS, "second instance destroyed successfully");

OK, thanks for testing! (suppose you've done this for v3).
I'm going to merge it today.

> For email CC, I have CC to you and Amir yesterday, please check.
You send extra mail on older version with info that you posted new version.
More effective is to use --cc parameter on git format-patch or git send-email in
new version (fewer mails + people don't have to search for particular email in
LTP mailing list mailbox).

Also, FYI we have archive on lore: https://lore.kernel.org/ltp/
(patchwork sometimes some mails).

Kind regards,
Petr

> Thanks very much!

> Gongyi

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

  reply	other threads:[~2021-11-23  8:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-23  7:09 [LTP] [PATCH v3] syscalls/fanotify07: Add stop_children() to cleanup() zhaogongyi via ltp
2021-11-23  8:12 ` Petr Vorel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-11-22  8:21 Zhao Gongyi via ltp
2021-11-23  5:40 ` Matthew Bobrowski via ltp

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=YZyiXbx5QOymJSsE@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=repnop@google.com \
    --cc=zhaogongyi@huawei.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.