public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Guangwen Feng <fenggw-fnst@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscalls/keyctl02: Add new regression test
Date: Fri, 3 Mar 2017 14:15:54 +0800	[thread overview]
Message-ID: <58B90A1A.7070509@cn.fujitsu.com> (raw)
In-Reply-To: <20170302141335.GB27525@rei.lan>

Hi!

Thanks for your review.

On 03/02/2017 10:13 PM, Cyril Hrubis wrote:
> Hi!
>> Fixed by:
>> commit b4a1b4f5047e4f54e194681125c74c0aa64d637d
>> Author: David Howells <dhowells@redhat.com>
>> Date:   Fri Dec 18 01:34:26 2015 +0000
>>
>>     KEYS: Fix race between read and revoke
> 
> Looks good, the original reproducer uses four threads instead of two
> though. Are two enough to crash the buggy kernel with 100% probability?

Sorry, after a large number of tests, I find that current code cannot
ensure the reproducibility.

Using four threads with 20000 loops can crash the buggy kernel with
almost 100% probability. and it still only takes 1s to test.
I will send a V2, thanks.


Tested on following kernel:

Reproduced:
===================
RHEL7.2GA
v4.4-rc5-168-g73796d8(commit 73796d8)
===================

Not reproduced:
===================
RHEL7.3Alpha
v4.4-rc5-169-gb4a1b4f(commit b4a1b4f)
===================

Best Regards,
Guangwen Feng



  reply	other threads:[~2017-03-03  6:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21  2:39 [LTP] [PATCH] syscalls/keyctl02: Add new regression test Guangwen Feng
2017-03-02 14:13 ` Cyril Hrubis
2017-03-03  6:15   ` Guangwen Feng [this message]
2017-03-03  8:07     ` [LTP] [PATCH v2] " Guangwen Feng
2017-03-03 10:08       ` 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=58B90A1A.7070509@cn.fujitsu.com \
    --to=fenggw-fnst@cn.fujitsu.com \
    --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