On Sat, Aug 11, 2018 at 9:40 AM Greg KH gregkh@linuxfoundation.org wrote:
On Mon, Aug 06, 2018 at 02:08:32PM -0700, Nick Desaulniers wrote:
These patches are needed for kasan+clang support. I confirmed they apply cleanly in order (top to bottom):
4.9: commit c5caf21ab0cf8 ("kasan: turn on -fsanitize-address-use-after-scope") commit 0e410e158e5b ("kasan: don't emit builtin calls when sanitization is off")
By applying these, I get a ton of new build warnings, so I can't add them :(
What? Such innocent patches.
$ git remote add stable git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git $ git checkout -b 4.9-stable-kasan stable/linux-4.9.y <git log shows 4.9.118> $ git cherry-pick c5caf21ab0cf8 $ git cherry-pick 0e410e158e5b $ make defconfig $ make -j46
I get -Wstringop-truncation, -Wstringop-overflow=, -Wpacked-not-aligned, -Warray-bounds warnings with gcc-8 with or without these patches.
Can you share your config, or what the warning was? Did I checkout the wrong branch?
4.4: commit c5caf21ab0cf8 ("kasan: turn on -fsanitize-address-use-after-scope")
I'm guessing I will get build warnings here too :(
===
0e410e158e5b is the one I'm interested in. Looks like it landed in 4.16, and got backported to 4.14-stable.
===
c5caf21ab0cf8 depends on c6d308534aef6 ("UBSAN: run-time undefined behavior sanity checker"), and I don't want to bring in all of UBSAN to 4.4. I'll send a patch for 0e410e158e5b.
I don't undersand, can you send a patch series for the patches you want to have applied? That makes it easier to understand.
Yes, sorry, I'll do that for 4.4 once we figure out what the 4.9 issues are.