From: Randy Dunlap <rdunlap@infradead.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
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 May 2 (objtool bug!)
Date: Wed, 2 May 2018 14:34:39 -0700 [thread overview]
Message-ID: <c425a9ed-3700-7019-b19c-4bdfd513892f@infradead.org> (raw)
In-Reply-To: <20180502210625.pehvcgtlqwqznnry@treble>
On 05/02/2018 02:06 PM, Josh Poimboeuf wrote:
> On Wed, May 02, 2018 at 08:59:38AM -0700, Randy Dunlap wrote:
>> On 05/02/2018 08:43 AM, Josh Poimboeuf wrote:
>>> On Wed, May 02, 2018 at 08:37:53AM -0700, Randy Dunlap wrote:
>>>> On 05/01/2018 11:59 PM, Stephen Rothwell wrote:
>>>>> Hi all,
>>>>>
>>>>> Changes since 20180501:
>>>>>
>>>>
>>>> on x86_64 randconfig:
>>>>
>>>> CC fs/cifs/smbencrypt.o
>>>> drivers/char/ipmi/ipmi_ssif.o: warning: objtool: return_hosed_msg()+0x0: infinite recursion (objtool bug!)
>>>> drivers/char/ipmi/ipmi_ssif.o: warning: objtool: deliver_recv_msg()+0x0: infinite recursion (objtool bug!)
>>>
>>> Can you share the object file (or at least the .config and GCC version)?
>>>
>>
>> gcc (SUSE Linux) 4.8.5
>>
>> config and .o file are attached.
>
> Thanks, can you verify this fixes it?
Yes, that's all good. Thanks.
Reported-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
--
~Randy
prev parent reply other threads:[~2018-05-02 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 6:59 linux-next: Tree for May 2 Stephen Rothwell
2018-05-02 15:37 ` linux-next: Tree for May 2 (objtool bug!) Randy Dunlap
2018-05-02 15:43 ` Josh Poimboeuf
2018-05-02 15:59 ` Randy Dunlap
2018-05-02 21:06 ` Josh Poimboeuf
2018-05-02 21:34 ` Randy Dunlap [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=c425a9ed-3700-7019-b19c-4bdfd513892f@infradead.org \
--to=rdunlap@infradead.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peterz@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
all inboxes | Powered by JetHome®