From: Michael Brade <brade@informatik.uni-muenchen.de>
To: linux-kernel@vger.kernel.org
Subject: found the reason for: utsrelease.h contains "CHK include/generated/utsrelease"
Date: Thu, 30 Jun 2011 22:30:25 +0200 [thread overview]
Message-ID: <201106302230.25239.brade@informatik.uni-muenchen.de> (raw)
Hi,
> I repeatedly get garbled output in utsrelease.h when compiling my own
> kernel.
> To reproduce:
>
> make mrproper
> make allnoconfig
> make prepare
>
> Output of "cat include/generated/utsrelease.h":
> CHK include/generated/utsrelease
I have spent many more hours analyzing this and finally found exactly what
causes this problem: doing "make prepare" under a running kernel with the
grsecurity/PAX option CONFIG_PAX_MEMORY_UDEREF set to Yes. I will post this in
the grsecurity forums as well, it seems to be their bug after all.
cheers,
Michael
reply other threads:[~2011-06-30 20:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201106302230.25239.brade@informatik.uni-muenchen.de \
--to=brade@informatik.uni-muenchen.de \
--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®