From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: linux-next: Tree for Apr 29 (objtool warning)
Date: Wed, 29 Apr 2020 10:01:44 -0500 [thread overview]
Message-ID: <20200429150144.l6raanbw5askynxp@treble> (raw)
In-Reply-To: <6b54b58f-b6f4-154f-e732-0b433741f1f6@infradead.org>
On Wed, Apr 29, 2020 at 07:50:10AM -0700, Randy Dunlap wrote:
> On 4/29/20 1:33 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20200428:
> >
>
> on x86_64:
>
> kernel/trace/trace_branch.o: warning: objtool: ftrace_likely_update()+0x3c4: call to __stack_chk_fail() with UACCESS enabled
>
> Full randconfig file is attached.
Peter, I think should __stack_chk_fail() be on the safe list?
--
Josh
prev parent reply other threads:[~2020-04-29 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 8:33 linux-next: Tree for Apr 29 Stephen Rothwell
2020-04-29 14:50 ` linux-next: Tree for Apr 29 (objtool warning) Randy Dunlap
2020-04-29 15:01 ` Josh Poimboeuf [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=20200429150144.l6raanbw5askynxp@treble \
--to=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).