From: David Laight <David.Laight@ACULAB.COM>
To: David Laight <David.Laight@ACULAB.COM>,
"'Leizhen (ThunderTown)'" <thunder.leizhen@huawei.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
Petr Mladek <pmladek@suse.com>,
Joe Lawrence <joe.lawrence@redhat.com>,
"live-patching@vger.kernel.org" <live-patching@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Alexei Starovoitov <ast@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Luis Chamberlain" <mcgrof@kernel.org>,
"linux-modules@vger.kernel.org" <linux-modules@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
"Ingo Molnar" <mingo@redhat.com>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: RE: [PATCH v9] kallsyms: Add self-test facility
Date: Fri, 16 Dec 2022 14:44:58 +0000 [thread overview]
Message-ID: <592dce7a0de24c62bd31c29f86ce6c1b@AcuMS.aculab.com> (raw)
In-Reply-To: <52450ec1da164d6d87587063c3b3d3d2@AcuMS.aculab.com>
From: David Laight
> Sent: 16 December 2022 13:30
>
> From: Leizhen (ThunderTown)
> > Sent: 16 December 2022 12:02
> >
> ..
> > > Moving the m68k version inside lib/string.c makes the test pass, too.
> > > So it must be related to the function being inline, and gcc making
> > > (incorrect) assumptions...
> >
> > Yes, it's the compiler's fault. I just replied David Laight:
> >
> > I added 'volatile' to prevent compiler optimizations, and it's OK now.
> >
> > diff --git a/arch/m68k/include/asm/string.h b/arch/m68k/include/asm/string.h
> > index f759d944c449940..3db81e5a783c72a 100644
> > --- a/arch/m68k/include/asm/string.h
> > +++ b/arch/m68k/include/asm/string.h
> > @@ -42,9 +42,9 @@ static inline char *strncpy(char *dest, const char *src, size_t n)
> > #define __HAVE_ARCH_STRCMP
> > static inline int strcmp(const char *cs, const char *ct)
> > {
> > - char res;
> > + signed char res;
> >
> > - asm ("\n"
> > + asm volatile ("\n"
> > "1: move.b (%0)+,%2\n" /* get *cs */
> > " cmp.b (%1)+,%2\n" /* compare a byte */
> > " jne 2f\n" /* not equal, break out */
>
> Adding 'volatile' there shouldn't make any real difference.
>
> I'd double-check the asm constraints for the two pointers.
> They are modified by the asm, but the caller's variables
> must not be changed.
>
> I think that means they need to be normal 'input' parameters
> and the result must be in different register (early clobber?).
> Currently the pointers are "+r" - which I think means they
> are input-output and any caller-supplied variable is
> likely to get changed.
Definitely badly broken.
'cs' and 'ct' should be input parameters.
'res' needs to be an early-clobber output parameter "=&r".
Since it is actually a 'static inline' (not just a #define)
then letting cs/ct be changed probably doesn't matter.
But the lack of 'early clobber' will cause grief.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2022-12-16 14:45 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 8:33 [PATCH v9] kallsyms: Add self-test facility Zhen Lei
2022-11-15 8:42 ` Luis Chamberlain
2022-11-15 8:43 ` Leizhen (ThunderTown)
2022-12-15 8:50 ` Geert Uytterhoeven
2022-12-15 9:16 ` Leizhen (ThunderTown)
2022-12-15 9:39 ` Geert Uytterhoeven
2022-12-15 12:33 ` Leizhen (ThunderTown)
2022-12-15 13:24 ` Geert Uytterhoeven
2022-12-15 13:58 ` Leizhen (ThunderTown)
2022-12-15 14:40 ` Leizhen (ThunderTown)
2022-12-15 14:51 ` Geert Uytterhoeven
2022-12-16 7:42 ` Leizhen (ThunderTown)
2022-12-16 9:36 ` Leizhen (ThunderTown)
2022-12-16 11:28 ` Geert Uytterhoeven
2022-12-16 12:01 ` Leizhen (ThunderTown)
2022-12-16 13:29 ` David Laight
2022-12-16 14:44 ` David Laight [this message]
2022-12-16 15:19 ` Andreas Schwab
2022-12-16 15:25 ` David Laight
2022-12-16 15:54 ` Andreas Schwab
2022-12-16 16:09 ` David Laight
2022-12-16 16:11 ` Andreas Schwab
2022-12-16 16:32 ` David Laight
2022-12-16 16:53 ` Steven Rostedt
2022-12-16 16:57 ` David Laight
2022-12-16 17:19 ` Steven Rostedt
2022-12-16 17:38 ` Steven Rostedt
2022-12-16 19:27 ` David Laight
2022-12-17 7:31 ` Leizhen (ThunderTown)
2022-12-17 13:37 ` Geert Uytterhoeven
2022-12-17 17:37 ` David Laight
2022-12-16 11:57 ` Andreas Schwab
2022-12-16 13:31 ` Leizhen (ThunderTown)
2022-12-16 13:47 ` Andreas Schwab
2022-12-15 14:43 ` Geert Uytterhoeven
2022-12-15 14:51 ` Andreas Schwab
2022-12-16 10:40 ` David Laight
2022-12-16 11:40 ` Leizhen (ThunderTown)
2022-12-16 11:44 ` Andreas Schwab
2022-12-16 11:57 ` Leizhen (ThunderTown)
2022-12-16 12:39 ` Andreas Schwab
2022-12-16 13:31 ` Leizhen (ThunderTown)
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=592dce7a0de24c62bd31c29f86ce6c1b@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=Jason@zx2c4.com \
--cc=akpm@linux-foundation.org \
--cc=ast@kernel.org \
--cc=geert@linux-m68k.org \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jolsa@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-modules@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mbenes@suse.cz \
--cc=mcgrof@kernel.org \
--cc=mingo@redhat.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=thunder.leizhen@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).