From: Borislav Petkov <bp@alien8.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
x86-ml <x86@kernel.org>
Subject: Re: [PATCH -v1.1] Kbuild: Ignore GREP_OPTIONS env variable
Date: Mon, 11 Nov 2013 21:58:38 +0100 [thread overview]
Message-ID: <20131111205837.GA29793@pd.tnic> (raw)
In-Reply-To: <20131111204330.GC18886@gmail.com>
On Mon, Nov 11, 2013 at 09:43:30PM +0100, Ingo Molnar wrote:
> * Michal Marek <mmarek@suse.cz> wrote:
> > On Mon, Nov 11, 2013 at 03:27:43PM +0100, Borislav Petkov wrote:
> > > From: Borislav Petkov <bp@suse.de>
> > > Subject: [PATCH] Kbuild: Ignore GREP_OPTIONS env variable
> > >
> > > When building the kernel in a shell which defines GREP_OPTIONS so that
> > > grep behavior is modified, we can break the generation of the syscalls
> > > table like so:
> > >
> > > __SYSCALL_COMMON(^[[01;31m^[[K0^[[m^[[K, sys_read, sys_read)
> > > __SYSCALL_COMMON(^[[01;31m^[[K1^[[m^[[K, sys_write, sys_write)
> > > __SYSCALL_COMMON(^[[01;31m^[[K1^[[m^[[K0, sys_mprotect, sys_mprotect) ...
> >
> > The email had literal escape sequences and git am preserved them, so git
> > show displayed red zeros and onces. [..]
>
> Neat trick if it was intentionally!
>
> > [...] That was quite scary, [...]
>
> Scary if it was unintentional ;-)
Yeah, all our computers are bleeding :-) Well, I sent the first version
on the evening before Helloween...
<scary music playing, an old door is creaking...>
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
prev parent reply other threads:[~2013-11-11 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 16:06 Kbuild: Ignore GREP_OPTIONS env variable Borislav Petkov
2013-11-06 21:42 ` Michal Marek
2013-11-11 14:27 ` [PATCH -v1.1] " Borislav Petkov
2013-11-11 17:00 ` Michal Marek
2013-11-11 20:43 ` Ingo Molnar
2013-11-11 20:58 ` Borislav Petkov [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=20131111205837.GA29793@pd.tnic \
--to=bp@alien8.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mmarek@suse.cz \
--cc=x86@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