From: David Laight <David.Laight@ACULAB.COM>
To: 'Guenter Roeck' <linux@roeck-us.net>,
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: Thu, 29 Feb 2024 22:19:20 +0000 [thread overview]
Message-ID: <b4fa177d6fcc42deb7db0dc0f9d36fe2@AcuMS.aculab.com> (raw)
In-Reply-To: <8403d8e3-c8ac-476b-8b8e-2c8b6ed8f464@roeck-us.net>
...
> >> 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.
Maybe because m68k only has 2 byte alignment for 32 bit items.
That causes grief in many places.
Although kmalloc() returning a larger alignment would fix some
of them without using much more memory?
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2024-02-29 22:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 23:57 Linux 6.8-rc6 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
2024-02-29 22:19 ` David Laight [this message]
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=b4fa177d6fcc42deb7db0dc0f9d36fe2@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=geert@linux-m68k.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux@roeck-us.net \
--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