From: Greg Ungerer <gerg@linux-m68k.org>
To: Daniel Palmer <daniel@thingy.jp>, geert@linux-m68k.org
Cc: linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k: nommu: fix memmove() with differently aligned src and dest for 68000
Date: Fri, 19 Dec 2025 21:58:54 +1000 [thread overview]
Message-ID: <d36788e2-52be-42b1-bb99-e2a18f99f7ce@linux-m68k.org> (raw)
In-Reply-To: <20251213120401.3992567-1-daniel@thingy.jp>
Hi Daniel,
On 13/12/25 22:04, Daniel Palmer wrote:
> 68000 has different alignment needs to 68020+.
> memcpy() checks if the destination is aligned and does a smaller copy
> to fix the alignment and then critically for 68000 it checks if the
> source is still unaligned and if it is reverts to smaller copies.
>
> memmove() does not currently do the second part and malfunctions if
> one of the pointers is aligned and the other isn't.
What is the nature of the failure, is it a trap?
> This is apparently getting triggered by printk. If I put breakpoints
> into the new checks added by this commit the first hit looks like this:
>
> memmove (n=205, src=0x2f3971 <printk_shared_pbufs+205>, dest=0x2f3980 <printk_shared_pbufs+220>) at arch/m68k/lib/memmove.c:82
>
> Signed-off-by: Daniel Palmer <daniel@thingy.jp>
Seems to make sense from what we have in memcpy.c.
Acked-by: Greg Ungerer <gerg@linux-m68k.org>
Geert: if you are ok with this I can take it via the m68knommu tree?
Regards
Greg
> ---
>
> This is from my "make 68000 work again" backlog.
>
> I have had this fix for years and I think the few other people that
> have various 68000 hobby builds must have something similar.
>
> /root # uname -a
> uClinux buildroot 6.18.0-12420-gdc1a468a2724 #120 Sat Dec 13 20:42:45 JST 2025 m68k GNU/Linux
> /root # cat /proc/cpuinfo
> CPU: 68000
> MMU: none
> FPU: none
> Clocking: 1179.1MHz
> BogoMips: 1758.00
> Calibration: 879001600 loops
> /root #
>
> arch/m68k/lib/memmove.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/arch/m68k/lib/memmove.c b/arch/m68k/lib/memmove.c
> index 6519f7f349f6..e33f00b02e4c 100644
> --- a/arch/m68k/lib/memmove.c
> +++ b/arch/m68k/lib/memmove.c
> @@ -24,6 +24,15 @@ void *memmove(void *dest, const void *src, size_t n)
> src = csrc;
> n--;
> }
> +#if defined(CONFIG_M68000)
> + if ((long)src & 1) {
> + char *cdest = dest;
> + const char *csrc = src;
> + for (; n; n--)
> + *cdest++ = *csrc++;
> + return xdest;
> + }
> +#endif
> if (n > 2 && (long)dest & 2) {
> short *sdest = dest;
> const short *ssrc = src;
> @@ -66,6 +75,15 @@ void *memmove(void *dest, const void *src, size_t n)
> src = csrc;
> n--;
> }
> +#if defined(CONFIG_M68000)
> + if ((long)src & 1) {
> + char *cdest = dest;
> + const char *csrc = src;
> + for (; n; n--)
> + *--cdest = *--csrc;
> + return xdest;
> + }
> +#endif
> if (n > 2 && (long)dest & 2) {
> short *sdest = dest;
> const short *ssrc = src;
next prev parent reply other threads:[~2025-12-19 11:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-13 12:04 [PATCH] m68k: nommu: fix memmove() with differently aligned src and dest for 68000 Daniel Palmer
2025-12-19 11:58 ` Greg Ungerer [this message]
2025-12-19 13:30 ` Daniel Palmer
2025-12-21 23:54 ` Eero Tamminen
2025-12-22 0:48 ` Daniel Palmer
2026-01-16 11:03 ` Greg Ungerer
2026-01-16 11:24 ` Daniel Palmer
2026-02-24 10:32 ` Geert Uytterhoeven
2026-02-25 10:04 ` Daniel Palmer
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=d36788e2-52be-42b1-bb99-e2a18f99f7ce@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=daniel@thingy.jp \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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