All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Schmidt <bernds_cb1@t-online.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	luke.yang@analog.com, gerg@snapgear.com
Subject: Re: Please revert git commit 1ad3dcc0
Date: Tue, 16 May 2006 17:10:03 +0200	[thread overview]
Message-ID: <4469EB4B.6000108@t-online.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0605160740070.3866@g5.osdl.org>

Linus Torvalds wrote:
> Side note: this would be a valid argument, except it's not always true. 
> I'm not sure why Luke wanted the fd in the first place, though, and 
> whether we want it.

The only reason was a failed LTP testcase which fills up the FD table 
and then called exec.

> Some loaders may actually want the fd value, see for example themisc 
> loader and MISC_FMT_OPEN_BINARY, and the ELF loader _does_ actually do it 
> for the (interpreter_type == INTERPRETER_AOUT) case.

The flat loader does not need a FD value.

>> Before the change, we didn't allocate or install a file descriptor, hence
>> there wasn't any reason to return EMFILE.  The spec at
>>   http://www.opengroup.org/onlinepubs/009695399/functions/exec.html
>> doesn't list EMFILE as a possible error.
> 
> Totally irrelevant.

I think it is relevant: if the spec does not require it, and the flat 
loader does not need the FD, then there is no reason to return EMFILE. 
Both conditions are true in this case.  If the spec did require it, then 
that would be an argument that the LTP testcase is valid, and for 
keeping the original patch.


Bernd

      reply	other threads:[~2006-05-16 15:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16 11:23 Please revert git commit 1ad3dcc0 Bernd Schmidt
2006-05-16 13:58 ` Andrew Morton
2006-05-16 14:29   ` Bernd Schmidt
2006-05-16 14:50     ` Andrew Morton
2006-05-16 14:57       ` Bernd Schmidt
2006-05-16 14:54     ` Linus Torvalds
2006-05-16 15:10       ` Bernd Schmidt [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=4469EB4B.6000108@t-online.de \
    --to=bernds_cb1@t-online.de \
    --cc=akpm@osdl.org \
    --cc=gerg@snapgear.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke.yang@analog.com \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.