[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4863CB8A.7000204@zytor.com>
Date: Thu, 26 Jun 2008 10:02:02 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Arnd Bergmann <arnd@...db.de>
CC: monstr@...nam.cz, linux-kernel@...r.kernel.org,
linux-arch@...r.kernel.org, stephen.neuendorffer@...inx.com,
John.Linn@...inx.com, john.williams@...alogix.com, matthew@....cx,
will.newton@...il.com, drepper@...hat.com,
microblaze-uclinux@...e.uq.edu.au, grant.likely@...retlab.ca,
linuxppc-dev@...abs.org, vapier.adi@...il.com,
alan@...rguk.ukuu.org.uk, Michal Simek <monstr@...str.eu>
Subject: Re: [PATCH 59/60] microblaze_v4: syscall_table.S and unistd.h
Arnd Bergmann wrote:
>
> You still set __NR_fork. There is no point defining the number if you
> can't actually call the syscall in the first place.
>
Worse, it is actively *harmful* to set the number; klibc or anything
that uses similar kinds of scripts for portability will see the symbol
and think the system call is available.
-hpa
--
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