From: Kees Cook <keescook@chromium.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: stackinit unit test failures on m68k
Date: Tue, 27 Feb 2024 14:19:07 -0800 [thread overview]
Message-ID: <202402271401.CB43AB2E8@keescook> (raw)
In-Reply-To: <CAMuHMdXMsxRRMV8g6+9vTy_4o8HF49SUh2deNdFjgKwDLEWrxQ@mail.gmail.com>
On Mon, Feb 12, 2024 at 09:34:02AM +0100, Geert Uytterhoeven wrote:
> Hi Günter,
>
> On Mon, Feb 12, 2024 at 12:06 AM Guenter Roeck <linux@roeck-us.net> wrote:
> > I see the following stackinit unit test failures on m68k when running
> > the q800 emulation.
> >
> > # test_char_array_zero: ASSERTION FAILED at lib/stackinit_kunit.c:333
> > Expected stackinit_range_contains(fill_start, fill_size, target_start, target_size) to be true, but is false
> > stack fill missed target!? (fill 16 wide, target offset by -12)
> >
> > # test_char_array_none: ASSERTION FAILED at lib/stackinit_kunit.c:343
> > Expected stackinit_range_contains(fill_start, fill_size, target_start, target_size) to be true, but is false
> > stack fill missed target!? (fill 16 wide, target offset by -12)
> >
> > Do you happen to know if this a problem with the test, with m68k, or maybe
> > with the configuration ? My configuration is based on mac_defconfig with
> > various test options enabled. I use gcc 11.4 to build the image. I tried
> > with qemu v8.1 and v8.2.
>
> Thanks, I see the same failures in the logs of my last testrun on ARAnyM, too.
> I haven't looked into the details yet.
>
> Only two failures does look like a nice improvement, compared to the
> previous time I ran that test ;-)
>
> https://lore.kernel.org/all/CAMuHMdX_g1tbiUL9PUQdqaegrEzCNN3GtbSvSBFYAL4TzvstFg@mail.gmail.com
This is complaining that the stack frames across subsequent calls to the
same leaf function don't end up putting the same variable in the same
place.
It's a rather difficult set of macros used try many different
combinations, but it's specifically talking about the "leaf_..."
function at line 208 of lib/stackinit_kunit.c. This test passes for all
the integral types, but seems to fail for a character array.
It is basically doing this:
static void *fill_start, *target_start;
static size_t fill_size, target_size;
static noinline int leaf_char_array_none(unsigned long sp, bool fill,
unsigned char *arg)
{
char buf[32];
unsigned char var[16];
target_start = &var;
target_size = sizeof(var);
/*
* Keep this buffer around to make sure we've got a
* stack frame of SOME kind...
*/
memset(buf, (char)(sp & 0xff), sizeof(buf));
/* Fill variable with 0xFF. */
if (fill) {
fill_start = &var;
fill_size = sizeof(var);
memset(fill_start,
(char)((sp & 0xff) | forced_mask),
fill_size);
}
/* Silence "never initialized" warnings. */
do_nothing_char_array(var);
/* Exfiltrate "var". */
memcpy(check_buf, target_start, target_size);
return (int)buf[0] | (int)buf[sizeof(buf) - 1];
}
and it's called as:
ignored = leaf_char_array_none((unsigned long)&ignored, 1, zero);
...
ignored = leaf_char_array_none((unsigned long)&ignored, 0, zero);
The first call remembers where "var" is in the stack frame via the
fill_start assignment, and the second call records where "var" is via
the target_start assignment.
The complaint is that it _changes_ between the two calls. ... Oh, I
think I see what's happened. Between the two calls, the stack grows (and
is for some reason not reclaimed) due to the KUNIT checks between the two
leaf calls. Yes, moving that fixes it.
I'll send a patch!
-Kees
--
Kees Cook
next prev parent reply other threads:[~2024-02-27 22:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 23:06 stackinit unit test failures on m68k Guenter Roeck
2024-02-12 8:34 ` Geert Uytterhoeven
2024-02-27 22:19 ` Kees Cook [this message]
2024-02-27 22:25 ` Kees Cook
2024-02-27 22:52 ` Andreas Schwab
2024-02-27 22:33 ` Finn Thain
2024-02-27 22:54 ` Guenter Roeck
2024-02-29 22:34 ` David Laight
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=202402271401.CB43AB2E8@keescook \
--to=keescook@chromium.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux@roeck-us.net \
/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