public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Matthew Bobrowski via ltp <ltp@lists.linux.it>
To: Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] syscalls/fanotify: Kill the child process before exit
Date: Fri, 5 Nov 2021 01:40:21 +0000	[thread overview]
Message-ID: <YYSLhTxZWpQLL745@google.com> (raw)
In-Reply-To: <YYQobypksa1GZPYo@pevik>

On Thu, Nov 04, 2021 at 07:37:35PM +0100, Petr Vorel wrote:
> Hi all,
> 
> > Before the main process exit abnormally, we need to kill
> > the child process.
> 
> Amir, Matthew, could you please have a look?

If anything, I feel as though stop_children() should probably be called
from cleanup() as that callback will be invoked if any of the
SAFE_FANOTIFY_* macros fail anyway, right?

I don't feel like there's a need to introduce another helper here to
explicitly handle the cleanup case, but I could also be wrong.

> > Signed-off-by: Zhao Gongyi <zhaogongyi@huawei.com>
> > ---
> >  .../kernel/syscalls/fanotify/fanotify07.c     | 35 ++++++++++++++++++-
> >  1 file changed, 34 insertions(+), 1 deletion(-)
> 
> > diff --git a/testcases/kernel/syscalls/fanotify/fanotify07.c b/testcases/kernel/syscalls/fanotify/fanotify07.c
> > index cc56d9019..0a0b4f1e4 100644
> > --- a/testcases/kernel/syscalls/fanotify/fanotify07.c
> > +++ b/testcases/kernel/syscalls/fanotify/fanotify07.c
> > @@ -108,6 +108,39 @@ static int setup_instance(void)
> >  	return fd;
> >  }
> 
> > +static int setup_another_instance(void)
> > +{
> > +	int rval;
> > +	int fd = fanotify_init(FAN_CLASS_CONTENT, O_RDONLY);
> > +
> > +	if (fd == -1) {
> > +		stop_children();
> > +		tst_brk(TBROK | TERRNO, "fanotify_init() failed");
> > +	}
> > +
> > +	if (fd < -1) {
> > +		stop_children();
> > +		tst_brk(TBROK | TERRNO,
> > +			"invalid fanotify_init() return %d", fd);
> > +	}
> > +
> > +	rval = fanotify_mark(fd,
> > +		FAN_MARK_ADD, FAN_ACCESS_PERM, AT_FDCWD, fname);
> > +
> > +	if (rval == -1) {
> > +		stop_children();
> > +		tst_brk(TBROK | TERRNO, "fanotify_mark() failed");
> > +	}
> > +
> > +	if (rval < -1) {
> > +		stop_children();
> > +		tst_brk(TBROK | TERRNO,
> > +			"invalid fanotify_mark() return %d", rval);
> > +	}
> > +
> > +	return fd;
> > +}
> > +
> >  static void loose_fanotify_events(void)
> >  {
> >  	int not_responded = 0;
> > @@ -160,7 +193,7 @@ static void test_fanotify(void)
> >  	 * Create and destroy another instance. This may hang if
> >  	 * unanswered fanotify events block notification subsystem.
> >  	 */
> > -	newfd = setup_instance();
> > +	newfd = setup_another_instance();
> 
> >  	SAFE_CLOSE(newfd);

/M

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

  reply	other threads:[~2021-11-05  1:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04 12:19 [LTP] [PATCH] syscalls/fanotify: Kill the child process before exit Zhao Gongyi
2021-11-04 18:37 ` Petr Vorel
2021-11-05  1:40   ` Matthew Bobrowski via ltp [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-11-05  2:22 zhaogongyi
2021-11-05  3:01 ` Matthew Bobrowski via ltp
2021-11-05  4:31   ` Amir Goldstein
2021-11-05  8:29     ` Petr Vorel
2021-11-05  8:12 ` Petr Vorel
2021-11-05  9:03 zhaogongyi

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=YYSLhTxZWpQLL745@google.com \
    --to=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    --cc=repnop@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox