From: Jan Kara <jack@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] fanotify: Add test for permission event destruction
Date: Tue, 14 Mar 2017 13:35:42 +0100 [thread overview]
Message-ID: <20170314123542.GA10831@quack2.suse.cz> (raw)
In-Reply-To: <20170314113633.GA4939@rei.lan>
On Tue 14-03-17 12:36:33, Cyril Hrubis wrote:
> Hi!
> > 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.
> >
> > Kernel crashes should be fixed by commit 96d41019e3ac "fanotify: fix
> > list corruption in fanotify_get_response()", kernel hangs by "fanotify:
> > Release SRCU lock when waiting for userspace response" (not yet landed
> > upstream).
>
> Ideally the testcase should include both commit ids in the test
> description as well. So either we wait until the fix gets into mainline,
> or add it later.
OK, I've addressed all other remarks and will wait with the testcase until
the fix gets merged.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2017-03-14 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 9:40 [LTP] [PATCH v2] fanotify: Add test for permission event destruction Jan Kara
2017-03-14 11:36 ` Cyril Hrubis
2017-03-14 12:35 ` Jan Kara [this message]
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=20170314123542.GA10831@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