From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 3/3] inotify06: kernel version check
Date: Wed, 2 Nov 2016 15:48:35 +0100 [thread overview]
Message-ID: <20161102144835.GC28344@rei.lan> (raw)
In-Reply-To: <1478087824-31577-4-git-send-email-dejan.jovicevic@rt-rk.com>
Hi!
> For test inotify06, kernels prior to 4.2 have a race when inode
> is being deleted while inotify group watching that inode is being
> torn down. When the race is hit, the kernel crashes or loops. So,
> added a check to see if the kernel is >= 4.2.0, and if not, the
> test breaks with TCONF and an appropriate message.
NO.
Bringing down broken kernel is exactly the whole point of the test.
Otherwise you cannot tell if the fix was backported to your kernel or
not.
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2016-11-02 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 11:57 [LTP] [PATCH 0/3] Additional checks for sched_xxx, socketcall01, inotify06 Dejan Jovicevic
2016-11-02 11:57 ` [LTP] [PATCH 1/3] sched_xxx: TCONF instead of TFAIL if user is not root Dejan Jovicevic
2016-11-02 14:07 ` Cyril Hrubis
2016-11-02 11:57 ` [LTP] [PATCH 2/3] socketcall: TCONF instead of TFAIL when " Dejan Jovicevic
2016-11-02 14:46 ` Cyril Hrubis
2016-11-02 11:57 ` [LTP] [PATCH 3/3] inotify06: kernel version check Dejan Jovicevic
2016-11-02 14:48 ` Cyril Hrubis [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=20161102144835.GC28344@rei.lan \
--to=chrubis@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