From: Finn Thain <fthain@telegraphics.com.au>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
kbuild test robot <lkp@intel.com>,
kbuild-all@01.org, linux-m68k <linux-m68k@lists.linux-m68k.org>,
Arnd Bergmann <arnd@arndb.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [m68k:master 1174/1174] arch/m68k/include/asm/string.h:72:25: warning: '__builtin_memcpy' forming offset 8 is out of the bounds [0, 7]
Date: Thu, 7 Mar 2019 13:59:33 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LNX.2.21.1903071329140.513@nippy.intranet> (raw)
In-Reply-To: <mvmh8chzo7j.fsf@linux-m68k.org>
On Tue, 5 Mar 2019, Andreas Schwab wrote:
> On Mar 05 2019, Finn Thain <fthain@telegraphics.com.au> wrote:
>
> > interesting that the kernel's strlen implementation in
> > include/linux/string.h can't achieve this.
>
> This implementation is only available if ARCH_HAS_FORTIFY_SOURCE.
>
I see. Perhaps we could add another definition to that file:
#if !defined(__NO_FORTIFY) && defined(__OPTIMIZE__) && defined(CONFIG_FORTIFY_SOURCE)
...
#else
__FORTIFY_INLINE __kernel_size_t strlen(const char *p)
{
return __builtin_strlen(p);
}
#endif
I didn't test that. But the following patch seems to work...
diff --git a/arch/m68k/include/asm/string.h b/arch/m68k/include/asm/string.h
index f759d944c449..3cff6b128ed3 100644
--- a/arch/m68k/include/asm/string.h
+++ b/arch/m68k/include/asm/string.h
@@ -71,4 +71,6 @@ extern void *memset(void *, int, __kernel_size_t);
extern void *memcpy(void *, const void *, __kernel_size_t);
#define memcpy(d, s, n) __builtin_memcpy(d, s, n)
+#define strlen(s) __builtin_strlen(s)
+
#endif /* _M68K_STRING_H_ */
diff --git a/lib/string.c b/lib/string.c
index 38e4ca08e757..fe970f2160e5 100644
--- a/lib/string.c
+++ b/lib/string.c
@@ -472,6 +472,7 @@ char *strim(char *s)
EXPORT_SYMBOL(strim);
#ifndef __HAVE_ARCH_STRLEN
+#undef strlen
/**
* strlen - Find the length of a string
* @s: The string to be sized
--
> Andreas.
>
>
next prev parent reply other threads:[~2019-03-07 2:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201903042049.npxcZzps%fengguang.wu@intel.com>
2019-03-04 13:05 ` Geert Uytterhoeven
2019-03-05 2:56 ` Finn Thain
2019-03-05 2:59 ` Finn Thain
2019-03-05 7:49 ` Geert Uytterhoeven
2019-03-05 8:58 ` Finn Thain
2019-03-05 9:03 ` Geert Uytterhoeven
2019-03-05 9:04 ` Andreas Schwab
2019-03-07 2:59 ` Finn Thain [this message]
2019-03-07 8:30 ` Geert Uytterhoeven
2019-03-07 21:43 ` Finn Thain
2019-03-11 9:14 ` Geert Uytterhoeven
2019-03-11 9:56 ` Andreas Schwab
2019-03-11 10:05 ` Geert Uytterhoeven
2019-03-11 10:13 ` Andreas Schwab
2019-03-11 10:20 ` Geert Uytterhoeven
2019-03-11 22:31 ` Finn Thain
2019-03-18 2:53 ` Finn Thain
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=alpine.LNX.2.21.1903071329140.513@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=lkp@intel.com \
--cc=schwab@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
all inboxes | Powered by JetHome®