public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Richard Palethorpe <rpalethorpe@suse.de>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscalls/keyctl05: new test for key_update() crash
Date: Tue, 01 Aug 2017 16:32:56 +0200	[thread overview]
Message-ID: <87d18fgxyf.fsf@our.domain.is.not.set> (raw)
In-Reply-To: <20170731210954.GB41369@gmail.com>


Hello Eric,

Eric Biggers writes:

> On Mon, Jul 31, 2017 at 10:57:56AM +0200, Richard Palethorpe wrote:
>> > +	for (i = 0; i < 10000; i++) {
>> > +		TEST(tst_syscall(__NR_keyctl, KEYCTL_UPDATE, keyid,
>> > +				 payload, sizeof(payload)));
>> > +		if (TEST_RETURN < 0 && TEST_ERRNO != EACCES) {
>> > +			tst_res(TFAIL | TTERRNO, "failed to update 'user' key");
>> > +			return;
>> > +		}
>> > +	}
>>
>> There is a library for causing race conditions (tst_fuzzy_sync.h), but
>> it only works with threads at the moment. I'm not entirely sure whether
>> to ask you to use it or not at this stage. How reliable is the test at
>> crashing a vulnerable system currently?
>>
>
> It happens either very reliably or not at all, depending on how the kernel stack
> is laid out which the test has no control over.  And if it *can* happen, it
> doesn't need any fancy synchronization to trigger the crash.
>
> (Also this test could use threads; it just seemed that forking was simpler.)
>
> Eric

OK, the updated patches look good to me. I may try refactoring the test
at some date to use the library, but there doesn't seem to be any reason
to do it at the moment.

--
Thank you,
Richard.

      reply	other threads:[~2017-08-01 14:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-29  1:07 [LTP] [PATCH] syscalls/keyctl05: new test for key_update() crash Eric Biggers
2017-07-31  8:57 ` Richard Palethorpe
2017-07-31 21:09   ` Eric Biggers
2017-08-01 14:32     ` Richard Palethorpe [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=87d18fgxyf.fsf@our.domain.is.not.set \
    --to=rpalethorpe@suse.de \
    --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