From: Vincent Whitchurch <Vincent.Whitchurch@axis.com>
To: Vincent Whitchurch <Vincent.Whitchurch@axis.com>,
"davidgow@google.com" <davidgow@google.com>,
"x86@kernel.org" <x86@kernel.org>
Cc: "dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
kernel <kernel@axis.com>,
"rafael.j.wysocki@intel.com" <rafael.j.wysocki@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"mingo@redhat.com" <mingo@redhat.com>,
"linux-um@lists.infradead.org" <linux-um@lists.infradead.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"andreyknvl@gmail.com" <andreyknvl@gmail.com>,
"anton.ivanov@cambridgegreys.com"
<anton.ivanov@cambridgegreys.com>,
"dvyukov@google.com" <dvyukov@google.com>,
"richard@nod.at" <richard@nod.at>,
"hpa@zytor.com" <hpa@zytor.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"ryabinin.a.a@gmail.com" <ryabinin.a.a@gmail.com>,
"frederic@kernel.org" <frederic@kernel.org>,
"bp@alien8.de" <bp@alien8.de>,
"glider@google.com" <glider@google.com>,
"vincenzo.frascino@arm.com" <vincenzo.frascino@arm.com>,
"kasan-dev@googlegroups.com" <kasan-dev@googlegroups.com>
Subject: Re: [PATCH] x86: Fix build of UML with KASAN
Date: Mon, 11 Sep 2023 07:26:00 +0000 [thread overview]
Message-ID: <f11475f922994b88f5adb14d23240716e16d5303.camel@axis.com> (raw)
In-Reply-To: <CABVgOS=X1=NC9ad+WV4spFFh4MBHLodhcyQ=Ks=6-FpXrbRTdA@mail.gmail.com>
On Sat, 2023-06-10 at 16:34 +0800, David Gow wrote:
> On Fri, 9 Jun 2023 at 19:19, Vincent Whitchurch
> <vincent.whitchurch@axis.com> wrote:
> >
> > Building UML with KASAN fails since commit 69d4c0d32186 ("entry, kasan,
> > x86: Disallow overriding mem*() functions") with the following errors:
> >
> > $ tools/testing/kunit/kunit.py run --kconfig_add CONFIG_KASAN=y
> > ...
> > ld: mm/kasan/shadow.o: in function `memset':
> > shadow.c:(.text+0x40): multiple definition of `memset';
> > arch/x86/lib/memset_64.o:(.noinstr.text+0x0): first defined here
> > ld: mm/kasan/shadow.o: in function `memmove':
> > shadow.c:(.text+0x90): multiple definition of `memmove';
> > arch/x86/lib/memmove_64.o:(.noinstr.text+0x0): first defined here
> > ld: mm/kasan/shadow.o: in function `memcpy':
> > shadow.c:(.text+0x110): multiple definition of `memcpy';
> > arch/x86/lib/memcpy_64.o:(.noinstr.text+0x0): first defined here
> >
> > If I'm reading that commit right, the !GENERIC_ENTRY case is still
> > supposed to be allowed to override the mem*() functions, so use weak
> > aliases in that case.
> >
> > Fixes: 69d4c0d32186 ("entry, kasan, x86: Disallow overriding mem*() functions")
> > Signed-off-by: Vincent Whitchurch <vincent.whitchurch@axis.com>
> > ---
>
> Thanks: I stumbled into this the other day and ran out of time to debug it.
>
> I've tested that it works here.
>
> Tested-by: David Gow <davidgow@google.com>
Thanks. Perhaps someone could pick this up? It's been a few months,
and the build problem is still present on v6.6-rc1.
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2023-09-11 7:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 11:18 [PATCH] x86: Fix build of UML with KASAN Vincent Whitchurch
2023-06-10 8:34 ` David Gow
2023-09-11 7:26 ` Vincent Whitchurch [this message]
2023-09-11 7:43 ` Richard Weinberger
2023-09-11 8:56 ` Peter Zijlstra
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=f11475f922994b88f5adb14d23240716e16d5303.camel@axis.com \
--to=vincent.whitchurch@axis.com \
--cc=andreyknvl@gmail.com \
--cc=anton.ivanov@cambridgegreys.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=davidgow@google.com \
--cc=dvyukov@google.com \
--cc=frederic@kernel.org \
--cc=glider@google.com \
--cc=hpa@zytor.com \
--cc=johannes@sipsolutions.net \
--cc=kasan-dev@googlegroups.com \
--cc=kernel@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=richard@nod.at \
--cc=ryabinin.a.a@gmail.com \
--cc=tglx@linutronix.de \
--cc=vincenzo.frascino@arm.com \
--cc=x86@kernel.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