[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190129173634.ee579795b227b141efc8bd30@linux-foundation.org>
Date: Tue, 29 Jan 2019 17:36:34 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Andrey Ryabinin <aryabinin@...tuozzo.com>
Cc: Anders Roxell <anders.roxell@...aro.org>, arnd@...db.de,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] lib/ubsan: default UBSAN_ALIGNMENT to not set
On Fri, 11 Jan 2019 22:01:16 +0300 Andrey Ryabinin <aryabinin@...tuozzo.com> wrote:
>
>
> On 12/17/18 6:03 PM, Anders Roxell wrote:
> > When booting an allmodconfig kernel, there are a lot of false-positives.
> > With a message like this 'UBSAN: Undefined behaviour in...' with a call
> > trace that follows.
> >
> > Reworked so that when building a allmodconfig kernel that turns
> > everything into '=m' or '=y' will turn off UBSAN_ALIGNMENT.
> >
> > Suggested-by: Arnd Bergmann <arnd@...db.de>
> > Signed-off-by: Anders Roxell <anders.roxell@...aro.org>
> > ---
>
> Acked-by: Andrey Ryabinin <aryabinin@...tuozzo.com>
>
Confused. Why does allmodconfig result in UBSAN warnings?
Powered by blists - more mailing lists