From: Steven Rostedt <rostedt@goodmis.org>
To: Tiejun Chen <tiejunc@vmware.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Julia Cartwright <julia@ni.com>, Daniel Wagner <wagi@monom.org>,
Tom Zanussi <zanussi@kernel.org>,
"srivatsa@csail.mit.edu" <srivatsa@csail.mit.edu>
Subject: Re: [ANNOUNCE] 4.19.106-rt45
Date: Fri, 27 Mar 2020 19:22:08 -0400 [thread overview]
Message-ID: <20200327192208.30bd16e5@gandalf.local.home> (raw)
In-Reply-To: <BYAPR05MB587828CEA4A259906BAD3AA5C5CC0@BYAPR05MB5878.namprd05.prod.outlook.com>
On Fri, 27 Mar 2020 23:16:51 +0000
Tiejun Chen <tiejunc@vmware.com> wrote:
> Steven,
>
> We cannot build this release (maybe all 4.19-rt) with CONFIG_UBSAN=y
Thanks for the report. I'll take a look at this on Monday.
-- Steve
> ----
> lib/ubsan.c: In function '__ubsan_handle_vla_bound_not_positive':
> lib/ubsan.c:348:2: error: too many arguments to function 'ubsan_prologue'
> ubsan_prologue(&data->location, &flags);
> ^~~~~~~~~~~~~~
> lib/ubsan.c:146:13: note: declared here
> static void ubsan_prologue(struct source_location *location)
> ^~~~~~~~~~~~~~
> lib/ubsan.c:353:2: error: too many arguments to function 'ubsan_epilogue'
> ubsan_epilogue(&flags);
> ^~~~~~~~~~~~~~
> lib/ubsan.c:155:13: note: declared here
> static void ubsan_epilogue(void)
> ^~~~~~~~~~~~~~
>
> I think you have to squash the following into patches/0309-lib-ubsan-Don-t-seralize-UBSAN-report.patch In your release.
>
> rebase onto [PATCH 309/326] lib/ubsan: Don't seralize UBSAN report
>
> Signed-off-by: Tiejun Chen <tiejunc@vmware.com>
>
prev parent reply other threads:[~2020-03-27 23:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 17:31 Steven Rostedt
2020-03-27 23:16 ` Tiejun Chen
2020-03-27 23:22 ` Steven Rostedt [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=20200327192208.30bd16e5@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=julia@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=srivatsa@csail.mit.edu \
--cc=tglx@linutronix.de \
--cc=tiejunc@vmware.com \
--cc=wagi@monom.org \
--cc=zanussi@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
all inboxes | Powered by JetHome®