mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Jann Horn <jann@thejh.net>,
	kbuild-all@01.org, James Morris <james.l.morris@oracle.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [kbuild-all] security/yama/yama_lsm.o: warning: objtool: report_access()+0x210: function has unreachable instruction
Date: Wed, 20 Jul 2016 09:12:16 +0800	[thread overview]
Message-ID: <20160720011216.GO17027@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <201607192204.fvKwcnpe%fengguang.wu@intel.com>

Hi Jann,

Sorry please ignore this one -- it looks like false warning from old
gcc 4.4 and 4.6 -- we just enabled old compiler tests triggered 10k
these warnings..

Thanks,
Fengguang

On Tue, Jul 19, 2016 at 10:20:05PM +0800, kbuild test robot wrote:
>tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>head:   47ef4ad2684d380dd6d596140fb79395115c3950
>commit: dca6b4149181baaa363b9a7ce7c550840bb3bc83 Yama: fix double-spinlock and user access in atomic context
>date:   8 weeks ago
>config: x86_64-randconfig-s2-07191718 (attached as .config)
>compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
>reproduce:
>        git checkout dca6b4149181baaa363b9a7ce7c550840bb3bc83
>        # save the attached .config to linux build tree
>        make ARCH=x86_64
>
>All warnings (new ones prefixed by >>):
>
>>> security/yama/yama_lsm.o: warning: objtool: report_access()+0x210: function has unreachable instruction
>
>---
>0-DAY kernel test infrastructure                Open Source Technology Center
>https://lists.01.org/pipermail/kbuild-all                   Intel Corporation


>_______________________________________________
>kbuild-all mailing list
>kbuild-all@lists.01.org
>https://lists.01.org/mailman/listinfo/kbuild-all

      reply	other threads:[~2016-07-20  1:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19 14:20 kbuild test robot
2016-07-20  1:12 ` Fengguang Wu [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=20160720011216.GO17027@wfg-t540p.sh.intel.com \
    --to=fengguang.wu@intel.com \
    --cc=james.l.morris@oracle.com \
    --cc=jann@thejh.net \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.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®