From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 0/4] ltp: add tests for some recently-fixed keyrings bugs
Date: Fri, 13 Oct 2017 09:25:12 +0200 [thread overview]
Message-ID: <20171013072512.wtblpsavplae4vuk@dell5510> (raw)
In-Reply-To: <20171012204227.116510-1-ebiggers3@gmail.com>
Hi Cyril,
> 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/cve | 1 +
> runtest/syscalls | 3 +
> testcases/kernel/syscalls/.gitignore | 3 +
> testcases/kernel/syscalls/add_key/add_key03.c | 98 +++++++++++++++++++++++++++
> testcases/kernel/syscalls/keyctl/keyctl06.c | 68 +++++++++++++++++++
> testcases/kernel/syscalls/keyctl/keyctl07.c | 89 ++++++++++++++++++++++++
...
This is going to create conflict with my patch-set v3 "Fix 32-bit cross compilation".
If you accept this first, I can rebase my patch-set for you.
BTW my patch-set is in github, if it's easier for you.
https://github.com/pevik/ltp/tree/autotools/fix-32bit-build.v3
Kind regards,
Petr
prev parent reply other threads:[~2017-10-13 7:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 20:42 [LTP] [PATCH v2 0/4] ltp: add tests for some recently-fixed keyrings bugs Eric Biggers
2017-10-12 20:42 ` [LTP] [PATCH v2 1/4] lapi/keyctl.h: add a few missing definitions Eric Biggers
2017-10-12 20:42 ` [LTP] [PATCH v2 2/4] syscalls/keyctl06: new test for keyring_read() buffer overrun Eric Biggers
2017-10-12 20:42 ` [LTP] [PATCH v2 3/4] syscalls/keyctl07: new test for oops when reading negative key Eric Biggers
2017-10-16 10:22 ` Cyril Hrubis
2017-10-16 19:47 ` Eric Biggers
2017-10-17 9:19 ` Cyril Hrubis
2017-10-12 20:42 ` [LTP] [PATCH v2 4/4] syscalls/add_key03: new test for forging user keyrings Eric Biggers
2017-10-13 7:25 ` Petr Vorel [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=20171013072512.wtblpsavplae4vuk@dell5510 \
--to=pvorel@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