mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	tipbuild@zytor.com, Ingo Molnar <mingo@kernel.org>
Subject: [tip:core/urgent 2/2] fs/ocfs2/alloc.o: warning: objtool: ocfs2_dinode_sanity_check()+0x12: duplicate frame pointer save
Date: Sat, 25 Feb 2017 06:13:48 +0800	[thread overview]
Message-ID: <201702250633.b7yWZPbq%fengguang.wu@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 902 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core/urgent
head:   d1091c7fa3d52ebce4dd3f15d04155b3469b2f90
commit: d1091c7fa3d52ebce4dd3f15d04155b3469b2f90 [2/2] objtool: Improve detection of BUG() and other dead ends
config: x86_64-randconfig-n0-02250449 (attached as .config)
compiler: gcc-4.8 (Debian 4.8.4-1) 4.8.4
reproduce:
        git checkout d1091c7fa3d52ebce4dd3f15d04155b3469b2f90
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All warnings (new ones prefixed by >>):

>> fs/ocfs2/alloc.o: warning: objtool: ocfs2_dinode_sanity_check()+0x12: duplicate frame pointer save
>> fs/ocfs2/alloc.o: warning: objtool: ocfs2_dinode_sanity_check()+0x0: frame pointer state mismatch

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 30114 bytes --]

                 reply	other threads:[~2017-02-24 22:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201702250633.b7yWZPbq%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=jpoimboe@redhat.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tipbuild@zytor.com \
    /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®