All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [digsig:next-ima-module 13/27] evm_crypto.c:(.text+0x300): multiple definition of `integrity_ini
Date: Mon, 06 Aug 2012 15:27:44 +0000	[thread overview]
Message-ID: <1344266864.9905.17.camel@falcor> (raw)
In-Reply-To: <20120806151604.GA7063@localhost>

On Mon, 2012-08-06 at 23:16 +0800, Fengguang Wu wrote:
> Hi Mimi,
> 
> Kernel build failed on
> 
> tree:    next-ima-module
> head:   a7d2a27e48c3d6b9b139728f0cdafc71e7640d47
> commit: 13c112b67029d66003085d6dc10e78b4e78108d0 [13/27] integrity: create and inititialize a keyring with builtin public key
> config: i386-randconfig-k621 (attached as .config)
> 
> All related error/warning messages:
> 
> security/integrity/evm/evm_crypto.o: In function `integrity_init_keyring':
> evm_crypto.c:(.text+0x300): multiple definition of `integrity_init_keyring'
> security/integrity/evm/evm_main.o:evm_main.c:(.text+0x360): first defined here
> security/integrity/evm/evm_secfs.o: In function `integrity_init_keyring':
> evm_secfs.c:(.text+0x140): multiple definition of `integrity_init_keyring'
> security/integrity/evm/evm_main.o:evm_main.c:(.text+0x360): first defined here

The patch ordering is wrong, but this isn't my tree.  Please let me
know, if/when this happens in my tree.

thanks,

Mimi


  reply	other threads:[~2012-08-06 15:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06 15:16 [digsig:next-ima-module 13/27] evm_crypto.c:(.text+0x300): multiple definition of `integrity_init_ke Fengguang Wu
2012-08-06 15:27 ` Mimi Zohar [this message]
2012-08-06 15:56 ` [digsig:next-ima-module 13/27] evm_crypto.c:(.text+0x300): multiple definition of `integrity_ini Kasatkin, Dmitry

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=1344266864.9905.17.camel@falcor \
    --to=zohar@linux.vnet.ibm.com \
    --cc=kernel-janitors@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 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.