[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jLsd3G3+PCwFSUGDxxbfnJwx8G8X4chH0WK21-kv+_ecA@mail.gmail.com>
Date: Thu, 13 Nov 2014 11:21:18 -0800
From: Kees Cook <keescook@...omium.org>
To: "Luck, Tony" <tony.luck@...el.com>
Cc: "yath@...h.de" <yath@...h.de>,
"ccross@...roid.com" <ccross@...roid.com>,
"anton@...msg.org" <anton@...msg.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-next <linux-next@...r.kernel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Jim Davis <jim.epost@...il.com>
Subject: Re: randconfig build error with next-20141113, in fs/pstore/inode.c
On Thu, Nov 13, 2014 at 11:18 AM, Luck, Tony <tony.luck@...el.com> wrote:
>> Building with the attached random configuration file,
>>
>> fs/built-in.o: In function `pstore_check_syslog_permissions':
>> inode.c:(.text+0x13a1bd): undefined reference to `check_syslog_permissions'
>> make: *** [vmlinux] Error 1
>
> Sebastian,
>
> This looks to come from your "Honor dmesg_restrict sysctl on dmesg dumps" patch
>
> The randconfig doesn't have CONFIG_PRINTK. I guess we need to provide a stub
> in <linux/syslog.h> to cover this.
Without CONFIG_PRINTK, check_syslog_permissions should probably fail.
-Kees
--
Kees Cook
Chrome OS Security
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists