linux-kernel - Re: PROBLEM: 2.6.21 - "make modules" with GREP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 17 May 2007 09:11:36 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Martin Christoph <mail@...a.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: 2.6.21 - "make modules" with GREP_OPTIONS="-C1" (and other)

On Thu, May 17, 2007 at 05:26:30AM +0200, Martin Christoph wrote:
> [1] Summary:
> If i have some GREP_OPTIONS set (like -C1 or other) i get several errors
> while trying to do "make modules".
> 
> [2] Full description:
> With some GREP_OPTIONS set "make modules" drops several errors like that:
> 
> root@...t /usr/src/linux # GREP_OPTIONS="-C1" make modules
>   CHK     include/linux/version.h
>   CHK     include/linux/utsrelease.h
>   Building modules, stage 2.
> [...]
> WARNING: "aes_enc_blk" [arch/i386/crypto/aes.ko] undefined!
> WARNING: "aes_dec_blk" [arch/i386/crypto/aes.ko] undefined!
> [...]
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
> 
> [3] Keywords:
> "make modules", "GREP_OPTIONS", "WARNING", "undefined"
> 
> [X.] Suggestion to fix:
> Unset GREP_OPTIONS within make process.

Thanks for reporting this - I gues this took some time to
find the root cause of the problem.

Albeit fixing it seems simple I will consider it for a
while. In the kernel we use several tools like:
awk, grep, perl, ls, rm, mv, cmp etc and then
we should audit all of these to check if similar
things could occur.

If someone steps up to do the check (including
all the tools I missed) I would be very grateful.

	Sam
-
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/