From: Arnd Bergmann <arnd@arndb.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andrey Ryabinin <aryabinin@virtuozzo.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH v2] ubsan: don't mark __ubsan_handle_builtin_unreachable as noreturn
Date: Wed, 7 Nov 2018 22:44:46 +0100 [thread overview]
Message-ID: <CAK8P3a23=C7joXFNr6P-1ap7Fkpz=umTAtHBH++YJ5VNC7AzzQ@mail.gmail.com> (raw)
In-Reply-To: <20181107125517.b5677f03a9a1978a5d179c9a@linux-foundation.org>
On Wed, Nov 7, 2018 at 9:55 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Wed, 7 Nov 2018 17:45:16 +0300 Andrey Ryabinin <aryabinin@virtuozzo.com> wrote:
>
> > From: Arnd Bergmann <arnd@arndb.de>
> > --- a/lib/ubsan.c
> > +++ b/lib/ubsan.c
> > @@ -427,8 +427,7 @@ void __ubsan_handle_shift_out_of_bounds(struct shift_out_of_bounds_data *data,
> > EXPORT_SYMBOL(__ubsan_handle_shift_out_of_bounds);
> >
> >
> > -void __noreturn
> > -__ubsan_handle_builtin_unreachable(struct unreachable_data *data)
> > +void __ubsan_handle_builtin_unreachable(struct unreachable_data *data)
> > {
> > unsigned long flags;
>
> This code has been here since 2016 and presumably people will want to
> build older kernels with newer gcc's. So I'll add cc:stable, OK?
>
Yes, sounds good. Thanks,
arnd
prev parent reply other threads:[~2018-11-07 21:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 15:47 [PATCH] ubsan: don't mark __ubsan_handle_builtin_unreachable as noreturn Arnd Bergmann
2018-02-05 9:02 ` Andrey Ryabinin
2018-02-05 10:15 ` Arnd Bergmann
2018-02-05 10:31 ` Andrey Ryabinin
2018-11-02 21:27 ` Olof Johansson
2018-11-07 14:44 ` Andrey Ryabinin
2018-11-07 14:45 ` [PATCH v2] " Andrey Ryabinin
2018-11-07 16:23 ` Olof Johansson
2018-11-07 20:55 ` Andrew Morton
2018-11-07 21:44 ` Arnd Bergmann [this message]
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='CAK8P3a23=C7joXFNr6P-1ap7Fkpz=umTAtHBH++YJ5VNC7AzzQ@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.