All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: kbuild test robot <fengguang.wu@intel.com>,
	kbuild-all@01.org, linux-kernel@vger.kernel.org,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: /tmp/ccTcF8pg.s: Error: .size expression for aes_p8_set_encrypt_key does not evaluate to a constant
Date: Thu, 21 Apr 2016 12:11:05 +0800	[thread overview]
Message-ID: <20160421041105.GB4659@intel.com> (raw)
In-Reply-To: <20160418150840.GA16356@redhat.com>

On Mon, Apr 18, 2016 at 05:08:41PM +0200, Oleg Nesterov wrote:
> On 04/17, kbuild test robot wrote:
> >
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head:   b9f5dba225aede4518ab0a7374c2dc38c7c049ce
> > commit: 5eeb50de42fd3251845d03c556db012267c72b3f uprobes: Change handle_trampoline() to flush the frames invalidated by longjmp()
> > date:   9 months ago
> 
> and this patch changed the single function in arch-neutral kernel/events/uprobes.c,
> this certainly looks like a false positive.

thanks for feedback, we will look into this to fix the false positive.

> 
> > config: powerpc-allyesconfig (attached as .config)
> > reproduce:
> >         wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> >         chmod +x ~/bin/make.cross
> >         git checkout 5eeb50de42fd3251845d03c556db012267c72b3f
> >         # save the attached .config to linux build tree
> >         make.cross ARCH=powerpc 
> > 
> > All errors (new ones prefixed by >>):
> > 
> >    /tmp/ccTcF8pg.s: Assembler messages:
> > >> /tmp/ccTcF8pg.s: Error: .size expression for aes_p8_set_encrypt_key does not evaluate to a constant
> > >> /tmp/ccTcF8pg.s: Error: .size expression for .aes_p8_set_encrypt_key does not evaluate to a constant
> > >> /tmp/ccTcF8pg.s: Error: .size expression for aes_p8_set_decrypt_key does not evaluate to a constant
> > >> /tmp/ccTcF8pg.s: Error: .size expression for .aes_p8_set_decrypt_key does not evaluate to a constant
> > >> /tmp/ccTcF8pg.s: Error: .size expression for aes_p8_encrypt does not evaluate to a constant
> > >> /tmp/ccTcF8pg.s: Error: .size expression for .aes_p8_encrypt does not evaluate to a constant
> > >> /tmp/ccTcF8pg.s: Error: .size expression for aes_p8_decrypt does not evaluate to a constant
> > >> /tmp/ccTcF8pg.s: Error: .size expression for .aes_p8_decrypt does not evaluate to a constant
> > >> /tmp/ccTcF8pg.s: Error: .size expression for aes_p8_cbc_encrypt does not evaluate to a constant
> > >> /tmp/ccTcF8pg.s: Error: .size expression for .aes_p8_cbc_encrypt does not evaluate to a constant
> > >> /tmp/ccTcF8pg.s: Error: .size expression for aes_p8_ctr32_encrypt_blocks does not evaluate to a constant
> > >> /tmp/ccTcF8pg.s: Error: .size expression for .aes_p8_ctr32_encrypt_blocks does not evaluate to a constant
> > --
> >    /tmp/ccB2I6Jo.s: Assembler messages:
> > >> /tmp/ccB2I6Jo.s: Error: .size expression for gcm_init_p8 does not evaluate to a constant
> > >> /tmp/ccB2I6Jo.s: Error: .size expression for .gcm_init_p8 does not evaluate to a constant
> > >> /tmp/ccB2I6Jo.s: Error: .size expression for gcm_gmult_p8 does not evaluate to a constant
> > >> /tmp/ccB2I6Jo.s: Error: .size expression for .gcm_gmult_p8 does not evaluate to a constant
> > >> /tmp/ccB2I6Jo.s: Error: .size expression for gcm_ghash_p8 does not evaluate to a constant
> > >> /tmp/ccB2I6Jo.s: Error: .size expression for .gcm_ghash_p8 does not evaluate to a constant
> > 
> > ---
> > 0-DAY kernel test infrastructure                Open Source Technology Center
> > https://lists.01.org/pipermail/kbuild-all                   Intel Corporation
> 
> 
> 

      reply	other threads:[~2016-04-21  4:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-17  5:18 /tmp/ccTcF8pg.s: Error: .size expression for aes_p8_set_encrypt_key does not evaluate to a constant kbuild test robot
2016-04-18 15:08 ` Oleg Nesterov
2016-04-21  4:11   ` Philip Li [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=20160421041105.GB4659@intel.com \
    --to=philip.li@intel.com \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.