mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Jakub Jelinek <jakub@redhat.com>
Cc: linux-kernel@vger.kernel.org, drepper@redhat.com
Subject: Re: [PATCH] Add getdents32t syscall
Date: Thu, 26 Feb 2004 15:15:25 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0402261504230.7830@ppc970.osdl.org> (raw)
In-Reply-To: <20040226223212.GA31589@devserv.devel.redhat.com>



On Thu, 26 Feb 2004, Jakub Jelinek wrote:
> 
> Userland struct dirent is:

Ahh. So with the new thing, you'd need no conversion at all.

> (since 1997 or so), so with the extended getdents syscall glibc would need
> to memmove every name by 1 byte.

The thing is, I hate encouraging glibc's behaviour of "we'll make up our
own structures", and then ask the kernel to fix it later when it was done
wrong in glibc. This is a totally new format that is totally unnecessary,
and the RIGHT thing to do is to have glibc just use the proper 64-bit
format.

In other words, why doesn't glibc ever just make a new major number and
make its "struct dirent" be the 64-bit version? It is _ridiculous_ to
carry this baggage around, and then complain and add MORE baggage to the
kernel because of having done things wrong the first time around.

			Linus

  reply	other threads:[~2004-02-26 23:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-26 19:38 Jakub Jelinek
2004-02-26 22:03 ` Randy.Dunlap
2004-02-26 22:15 ` Linus Torvalds
2004-02-26 22:25   ` Linus Torvalds
2004-02-26 22:29     ` Ulrich Drepper
2004-02-26 23:00       ` Linus Torvalds
2004-02-26 22:32     ` Jakub Jelinek
2004-02-26 23:15       ` Linus Torvalds [this message]
2004-02-27  1:33         ` Ulrich Drepper
2004-02-27  6:16           ` Linus Torvalds
2004-02-27  7:05             ` Ulrich Drepper
2004-02-28 23:21           ` Jamie Lokier
2004-02-27  1:46         ` Andreas Dilger
2004-02-27  3:36       ` Theodore Ts'o
2004-02-29  0:25   ` Jamie Lokier
2004-02-27 19:28 ` Linus Torvalds

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=Pine.LNX.4.58.0402261504230.7830@ppc970.osdl.org \
    --to=torvalds@osdl.org \
    --cc=drepper@redhat.com \
    --cc=jakub@redhat.com \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®