From: Alexander Popov <alex.popov@linux.com>
To: Kees Cook <keescook@chromium.org>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Cc: notify@kernel.org
Subject: Re: [PATCH v1 1/1] lkdtm/stackleak: Make the stack erasing test more verbose
Date: Sat, 28 Dec 2019 23:20:47 +0300 [thread overview]
Message-ID: <7d692333-7ff8-0c3f-8e36-dd2cc0ff3163@linux.com> (raw)
In-Reply-To: <20191219145416.435508-1-alex.popov@linux.com>
Hello!
Just a friendly ping.
Could I have the feedback for this patch?
Best regards,
Alexander
On 19.12.2019 17:54, Alexander Popov wrote:
> Make the stack erasing test more verbose about the errors that it
> can detect. BUG() in case of test failure is useful when the test
> is running in a loop.
>
> Signed-off-by: Alexander Popov <alex.popov@linux.com>
> ---
> drivers/misc/lkdtm/stackleak.c | 25 +++++++++++++++++--------
> 1 file changed, 17 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/misc/lkdtm/stackleak.c b/drivers/misc/lkdtm/stackleak.c
> index d5a084475abc..d198de4d4c7e 100644
> --- a/drivers/misc/lkdtm/stackleak.c
> +++ b/drivers/misc/lkdtm/stackleak.c
> @@ -16,6 +16,7 @@ void lkdtm_STACKLEAK_ERASING(void)
> unsigned long *sp, left, found, i;
> const unsigned long check_depth =
> STACKLEAK_SEARCH_DEPTH / sizeof(unsigned long);
> + bool test_failed = false;
>
> /*
> * For the details about the alignment of the poison values, see
> @@ -34,7 +35,8 @@ void lkdtm_STACKLEAK_ERASING(void)
> left--;
> } else {
> pr_err("FAIL: not enough stack space for the test\n");
> - return;
> + test_failed = true;
> + goto end;
> }
>
> pr_info("checking unused part of the thread stack (%lu bytes)...\n",
> @@ -52,22 +54,29 @@ void lkdtm_STACKLEAK_ERASING(void)
> }
>
> if (found <= check_depth) {
> - pr_err("FAIL: thread stack is not erased (checked %lu bytes)\n",
> + pr_err("FAIL: the erased part is not found (checked %lu bytes)\n",
> i * sizeof(unsigned long));
> - return;
> + test_failed = true;
> + goto end;
> }
>
> - pr_info("first %lu bytes are unpoisoned\n",
> + pr_info("the erased part begins after %lu not poisoned bytes\n",
> (i - found) * sizeof(unsigned long));
>
> /* The rest of thread stack should be erased */
> for (; i < left; i++) {
> if (*(sp - i) != STACKLEAK_POISON) {
> - pr_err("FAIL: thread stack is NOT properly erased\n");
> - return;
> + pr_err("FAIL: bad value number %lu in the erased part: 0x%lx\n",
> + i, *(sp - i));
> + test_failed = true;
> }
> }
>
> - pr_info("OK: the rest of the thread stack is properly erased\n");
> - return;
> +end:
> + if (test_failed) {
> + pr_err("FAIL: the thread stack is NOT properly erased\n");
> + BUG();
> + } else {
> + pr_info("OK: the rest of the thread stack is properly erased\n");
> + }
> }
>
next prev parent reply other threads:[~2019-12-28 20:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 14:54 [PATCH v1 1/1] lkdtm/stackleak: Make the stack erasing test more verbose Alexander Popov
2019-12-28 20:20 ` Alexander Popov [this message]
2019-12-30 18:37 ` Kees Cook
2019-12-30 22:20 ` Alexander Popov
2019-12-30 22:46 ` Kees Cook
2020-01-01 23:26 ` Alexander Popov
2020-01-02 22:03 ` Kees Cook
2020-01-02 22:37 ` Alexander Popov
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=7d692333-7ff8-0c3f-8e36-dd2cc0ff3163@linux.com \
--to=alex.popov@linux.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=notify@kernel.org \
/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