From: Eric Biggers <ebiggers3@gmail.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 0/4] ltp: add tests for some recently-fixed keyrings bugs
Date: Tue, 10 Oct 2017 10:51:16 -0700 [thread overview]
Message-ID: <20171010175120.90586-1-ebiggers3@gmail.com> (raw)
From: Eric Biggers <ebiggers@google.com>
Add tests to LTP for a few more longstanding bugs which were recently
fixed in the kernel keyrings API.
Eric Biggers (4):
lapi/keyctl.h: add a few missing definitions
syscalls/keyctl06: new test for keyring_read() buffer overrun
syscalls/keyctl07: new test for oops when reading negative key
syscalls/add_key03: new test for forging user keyrings
include/lapi/keyctl.h | 20 +++++
runtest/syscalls | 3 +
testcases/kernel/syscalls/.gitignore | 3 +
testcases/kernel/syscalls/add_key/add_key03.c | 122 ++++++++++++++++++++++++++
testcases/kernel/syscalls/keyctl/keyctl06.c | 68 ++++++++++++++
testcases/kernel/syscalls/keyctl/keyctl07.c | 89 +++++++++++++++++++
6 files changed, 305 insertions(+)
create mode 100644 testcases/kernel/syscalls/add_key/add_key03.c
create mode 100644 testcases/kernel/syscalls/keyctl/keyctl06.c
create mode 100644 testcases/kernel/syscalls/keyctl/keyctl07.c
--
2.14.2.920.gcf0c67979c-goog
next reply other threads:[~2017-10-10 17:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 17:51 Eric Biggers [this message]
2017-10-10 17:51 ` [LTP] [PATCH 1/4] lapi/keyctl.h: add a few missing definitions Eric Biggers
2017-10-10 17:51 ` [LTP] [PATCH 2/4] syscalls/keyctl06: new test for keyring_read() buffer overrun Eric Biggers
2017-10-10 17:51 ` [LTP] [PATCH 3/4] syscalls/keyctl07: new test for oops when reading negative key Eric Biggers
2017-10-10 17:51 ` [LTP] [PATCH 4/4] syscalls/add_key03: new test for forging user keyrings Eric Biggers
2017-10-11 13:47 ` Cyril Hrubis
2017-10-11 13:53 ` 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=20171010175120.90586-1-ebiggers3@gmail.com \
--to=ebiggers3@gmail.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