linux-kernel - Re: [RFC PATCH] ARM Fix /usr/bin/xargs: etags: Argument list too long

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 08 Aug 2012 16:41:52 +0200
From:	Michal Marek <mmarek@...e.cz>
To:	David Cullen <David.Cullen@...-americas.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH] ARM Fix /usr/bin/xargs: etags: Argument list too
 long

Dne 8.8.2012 16:32, David Cullen napsal(a):
> Patch applies to
> 
>     commit 42a579a0f960081cd16fc945036e4780c3ad3202
> 
> When running "make ARCH=arm TAGS" in a chroot using qemu-arm-static,
> the following message is emitted:
> 
>     [user@...t:/home/work/linux]: make ARCH=arm TAGS
>       GEN     TAGS
>     /usr/bin/xargs: etags: Argument list too long
> 
> This can be fixed by by passing "-L 1024" to xargs in scripts/tags.sh.
> 
> The "1024" was a guess. A value of "3862" changes the message to
> 
>     /usr/bin/xargs: argument list too long
> 
> Using "2048" also fixes the problem. However, I don't know how much
> headroom that leaves
> 
> Does anyone know why the argument lists must be shorter for ARM? All
> of the documentation I have available says that 4096 should be the
> limit.

This looks like a bug in xargs, it should make sure that the commandline
fits into ARG_MAX. BTW, a better workaround would be to use the -s
option, which limits the size of the argument list.

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