From: Arnd Bergmann <arnd@arndb.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Nicolas Pitre <nicolas.pitre@linaro.org>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] branch tracer: fix freak link error
Date: Mon, 15 Feb 2016 21:15:39 +0100 [thread overview]
Message-ID: <2535125.MjntUgx4sh@wuerfel> (raw)
In-Reply-To: <20160215124746.44e8c2d0@gandalf.local.home>
On Monday 15 February 2016 12:47:46 Steven Rostedt wrote:
> On Fri, 12 Feb 2016 22:26:42 +0100
> Arnd Bergmann <arnd@arndb.de> wrote:
>
> > In my randconfig tests, I came across a bug that involves several
> > components:
> >
> >
>
> [..]
>
> >
> > This patch avoids the problem by changing __trace_if() to check
> > whether the condition is known at compile-time to be nonzero, rather
> > than checking whether it is actually a constant.
> >
> > I see this one link error in roughly one out of 1600 randconfig builds
> > on ARM, and the patch fixes all known instances.
> >
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> > Fixes: ab3c9c686e22 ("branch tracer, intel-iommu: fix build with CONFIG_BRANCH_TRACER=y")
>
> Want me to pull this into my queue? I have another patch I need to send
> to Linus and I can add this in that pull request.
That would be nice, yes.
Do you also want to add a 'Cc: stable@vger.kernel.org' tag?
Arnd
next prev parent reply other threads:[~2016-02-15 20:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 21:26 [PATCH] branch tracer: fix freak link error Arnd Bergmann
2016-02-12 21:45 ` Nicolas Pitre
2016-02-12 21:49 ` Arnd Bergmann
2016-02-12 21:52 ` Arnd Bergmann
2016-02-12 22:12 ` Steven Rostedt
2016-02-12 22:18 ` Arnd Bergmann
2016-02-15 17:47 ` Steven Rostedt
2016-02-15 20:15 ` Arnd Bergmann [this message]
2016-02-15 20:26 ` Steven Rostedt
2016-02-16 9:17 ` Arnd Bergmann
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=2535125.MjntUgx4sh@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=mingo@redhat.com \
--cc=nicolas.pitre@linaro.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).