From: Jan Kara <jack@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] fanotify: Add test for permission event destruction
Date: Mon, 23 Jan 2017 12:07:26 +0100 [thread overview]
Message-ID: <20170123110726.GA5421@quack2.suse.cz> (raw)
In-Reply-To: <CAOQ4uxhjP7gpC7gzWJPRsKQO1b2SsspPa5TprqLc9+6fvvxh1Q@mail.gmail.com>
On Sat 21-01-17 17:47:21, Amir Goldstein wrote:
> On Fri, Jan 20, 2017 at 3:29 PM, Jan Kara <jack@suse.cz> wrote:
> > Test whether kernel's notification subsystem gets stuck when some
> > fanotify permission events are not responded to. Also test destruction
> > of fanotify instance while there are outstanding permission events. This
> > can result in hanging of processes indefinitely in kernel or in kernel
> > crashes.
> >
>
> Looks good to me, but I wonder about your phrasing "can result" and
> "This may hang" below.
The hang happens always, it is just too lax wording of the changelog...
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2017-01-23 11:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 13:29 [LTP] [PATCH] fanotify: Add test for permission event destruction Jan Kara
2017-01-21 15:47 ` Amir Goldstein
2017-01-23 11:07 ` Jan Kara [this message]
2017-01-23 12:19 ` Cyril Hrubis
2017-01-24 12:13 ` Jan Kara
2017-01-24 13:00 ` Cyril Hrubis
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=20170123110726.GA5421@quack2.suse.cz \
--to=jack@suse.cz \
--cc=ltp@lists.linux.it \
/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