From: Sodagudi Prasad <psodagud@codeaurora.org>
To: aryabinin@virtuozzo.com, nicolas.iooss_linux@m4x.org,
akpm@linux-foundation.org, mingo@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: __ubsan_handle_type_mismatch converted to __ubsan_handle_type_mismatch_v1
Date: Thu, 05 Oct 2017 19:29:41 -0700 [thread overview]
Message-ID: <f4a6641103be0c520a373f3ad132a20a@codeaurora.org> (raw)
Hi All,
Based on below links __ubsan_handle_type_mismatch has been renamed to
__ubsan_handle_type_mismatch_v1.
https://github.com/llvm-mirror/compiler-rt/commit/56faee71af1888ba12ab076b3d1f9bbe223493df#diff-21369cc6f3917b27df3ced8de89cf134
https://www.mail-archive.com/gcc-bugs@gcc.gnu.org/msg535130.html
When I tried to compile the kernel with LLVM seen following errors.
arch/arm64/kernel/traps.o: In function `dump_backtrace':
kernel/arch/arm64/kernel/traps.c:192: undefined reference to
`__ubsan_handle_type_mismatch_v1'
kernel/arch/arm64/kernel/traps.c:192: undefined reference to
`__ubsan_handle_type_mismatch_v1'
kernel/arch/arm64/kernel/traps.c:192: undefined reference to
`__ubsan_handle_type_mismatch_v1'
kernel/arch/arm64/kernel/traps.c:192: undefined reference to
`__ubsan_handle_type_mismatch_v1'
arch/arm64/kernel/traps.o: In function `dump_mem':
Can I add __ubsan_handle_type_mismatch_v1 API similar to
__ubsan_handle_type_mismatch()(I will send path for review)?
If both apis are present, then there will be backward compatibility.
Let me know if you have any other suggestions for this issue.
-Thanks, Prasad
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum,
Linux Foundation Collaborative Project
next reply other threads:[~2017-10-06 2:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 2:29 Sodagudi Prasad [this message]
2017-10-06 8:45 ` Andrey Ryabinin
2017-10-10 7:06 ` [PATCH] UBSAN: Add __ubsan_handle_type_mismatch_v1 handler Prasad Sodagudi
2017-10-10 12:22 ` Andrey Ryabinin
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=f4a6641103be0c520a373f3ad132a20a@codeaurora.org \
--to=psodagud@codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nicolas.iooss_linux@m4x.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
Powered by JetHome