From: Greg KH <gregkh@linuxfoundation.org>
To: Andrey Konovalov <andreyknvl@google.com>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
stable <stable@vger.kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Dmitry Vyukov <dvyukov@google.com>
Subject: Re: kasan patches
Date: Tue, 14 Aug 2018 15:51:09 +0200 [thread overview]
Message-ID: <20180814135109.GC29843@kroah.com> (raw)
In-Reply-To: <CAAeHK+xx7Ozy2SSiN=22BkjAandjC0FY9jhAwm97RvDRLcqNQQ@mail.gmail.com>
On Tue, Aug 14, 2018 at 02:44:19PM +0200, Andrey Konovalov wrote:
> On Tue, Aug 14, 2018 at 9:37 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Tue, Aug 14, 2018 at 09:24:29AM +0200, Greg KH wrote:
> >> On Mon, Aug 13, 2018 at 02:25:12PM -0700, Nick Desaulniers wrote:
> >> > 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?
> >>
> >> I used 'make allmodconfig' on a x86 Fedora 27 release which is using gcc
> >> 7.3.1. Adding those patches adds a ton of warnings. Let me go do a
> >> test build and send you the full log...
> >
> > Attached is the full build log. Before those 2 patches were added, no
> > build warnings. Afterward, I now have 148 build warnings. So something
> > is not right here.
>
> I think the issue here is that e7c52b84fb ("kasan: rework Kconfig
> settings") should have been backported after c5caf21ab0cf8 ("kasan:
> turn on -fsanitize-address-use-after-scope"). You'll need to
> "rebackport" the former one (hide use-after-scope under
> CONFIG_KASAN_EXTRA and set FRAME_WARN to 3072 with KASAN_EXTRA).
Again, if someone could send me a patch series that are properly
backported, it would make everything a lot easier and allow these
patches to actually be applied :)
thanks,
greg k-h
next prev parent reply other threads:[~2018-08-14 16:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 21:08 kasan patches Nick Desaulniers
2018-08-11 16:40 ` Greg KH
2018-08-13 21:25 ` Nick Desaulniers
2018-08-14 7:24 ` Greg KH
2018-08-14 7:37 ` Greg KH
2018-08-14 12:44 ` Andrey Konovalov
2018-08-14 13:51 ` Greg KH [this message]
2018-08-14 20:33 ` Nick Desaulniers
2018-08-14 20:56 ` Arnd Bergmann
2018-08-14 22:04 ` Nick Desaulniers
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=20180814135109.GC29843@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreyknvl@google.com \
--cc=dvyukov@google.com \
--cc=ndesaulniers@google.com \
--cc=samitolvanen@google.com \
--cc=stable@vger.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