From: Guenter Roeck <linux@roeck-us.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kees Cook <keescook@chromium.org>,
linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: Linux 6.8-rc6
Date: Tue, 27 Feb 2024 06:17:20 -0800 [thread overview]
Message-ID: <8403d8e3-c8ac-476b-8b8e-2c8b6ed8f464@roeck-us.net> (raw)
In-Reply-To: <CAMuHMdVYjw9CEBUzxuJ-10wudK_mvJZgqP3gR4kuv-FDYBZ-Aw@mail.gmail.com>
On 2/26/24 23:41, Geert Uytterhoeven wrote:
> Hi Günter,
>
> CC Kees
>
> On Mon, Feb 26, 2024 at 6:52 PM Guenter Roeck <linux@roeck-us.net> wrote:
>> stackinit
>> ---------
>>
>> Seen with m68k: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)
>>
>> Report:
>> https://lore.kernel.org/lkml/a0d10d50-2720-4ecd-a2c6-c2c5e5aeee65@roeck-us.net/
>
> I don't think these have ever succeeded before, see
> https://lore.kernel.org/all/CAMuHMdX_g1tbiUL9PUQdqaegrEzCNN3GtbSvSBFYAL4TzvstFg@mail.gmail.com
>
>> I suspect this may be caused by the test assuming that stack growth is
>> downward, but I don't really understand the test well enough to be sure.
>> I'll disable this set of tests for m68k going forward, so I am not going
>> to report the problem again in the future.
>
> On m68k, the stack does grow downward.
Sorry, I meant to say upward, but apparently I was wrong.
> AFAIK only parisc has a stack that grows upward.
>
... and the tests work there, so that isn't the problem.
As mentioned, I stopped running those tests on m68k.
Thanks,
Guenter
next prev parent reply other threads:[~2024-02-27 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 23:57 Linus Torvalds
2024-02-26 8:12 ` Build regressions/improvements in v6.8-rc6 Geert Uytterhoeven
2024-02-26 8:41 ` Geert Uytterhoeven
2024-02-26 9:14 ` Linux 6.8-rc6 Luna Jernberg
2024-02-26 17:51 ` Guenter Roeck
2024-02-27 7:41 ` Geert Uytterhoeven
2024-02-27 14:17 ` Guenter Roeck [this message]
2024-02-29 22:19 ` David Laight
2024-02-29 22:24 ` John Paul Adrian Glaubitz
2024-02-29 23:07 ` Andreas Schwab
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=8403d8e3-c8ac-476b-8b8e-2c8b6ed8f464@roeck-us.net \
--to=linux@roeck-us.net \
--cc=geert@linux-m68k.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®