From: Randy Dunlap <randy.dunlap@oracle.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
James Morris <jmorris@namei.org>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
Serge Hallyn <serue@us.ibm.com>
Subject: Re: ima changes to shmem breaks !CONFIG_SHMEM
Date: Mon, 09 Feb 2009 13:56:50 -0800 [thread overview]
Message-ID: <4990A6A2.90107@oracle.com> (raw)
In-Reply-To: <8bd0f97a0902091351p4a719809gf1f2119735f0430f@mail.gmail.com>
Mike Frysinger wrote:
> On Mon, Feb 9, 2009 at 16:49, Randy Dunlap wrote:
>> Mike Frysinger wrote:
>>> On Mon, Feb 9, 2009 at 16:23, James Morris wrote:
>>>> On Mon, 9 Feb 2009, Mike Frysinger wrote:
>>>>> commit 1df9f0a73178718969ae47d813b8e7aab2cf073c broke default building
>>>>> for Blackfin systems:
>>>>> CC mm/shmem.o
>>>>> mm/shmem.c: In function 'shmem_zero_setup':
>>>>> mm/shmem.c:2670: error: implicit declaration of function 'ima_shm_check'
>>>>> make[1]: *** [mm/shmem.o] Error 1
>>>>>
>>>>> that's because the ima.h include was added behind the CONFIG_SHMEM
>>>>> markings rather than everywhere, just like the function is used.
>>>> Does this seem like the correct fix?
>>> it converts the build error to a build warning:
>>> CC mm/shmem.o
>>> In file included from mm/shmem.c:32:
>>> include/linux/ima.h:25: warning: 'struct linux_binprm' declared inside
>>> parameter list
>>> include/linux/ima.h:25: warning: its scope is only this definition or
>>> declaration, which is probably not what you want
>> Add to the other patch:
>>
>> --- linux-next-20090209.orig/include/linux/ima.h
>> +++ linux-next-20090209/include/linux/ima.h
>> @@ -8,6 +8,7 @@
>> */
>>
>> #include <linux/fs.h>
>> +struct linux_binprm;
>>
>> #ifndef _LINUX_IMA_H
>> #define _LINUX_IMA_H
>>
>>
>>
>> and it builds for me.
>
> yes, it builds w/out warnings now for me too. any reason those are
> outside of _LINUX_IMA_H ? looks like they should both be inside of
> that.
Agreed, that change is also good.
Thanks.
--
~Randy
next prev parent reply other threads:[~2009-02-09 21:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 16:30 ima changes to shmem breaks !CONFIG_SHMEM Mike Frysinger
2009-02-09 21:23 ` James Morris
2009-02-09 21:27 ` Mike Frysinger
2009-02-09 21:49 ` Randy Dunlap
2009-02-09 21:51 ` Mike Frysinger
2009-02-09 21:56 ` Randy Dunlap [this message]
2009-02-09 23:59 ` Mimi Zohar
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=4990A6A2.90107@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=serue@us.ibm.com \
--cc=vapier.adi@gmail.com \
--cc=zohar@linux.vnet.ibm.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