[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201006301131.37241.arnd@arndb.de>
Date: Wed, 30 Jun 2010 11:31:37 +0200
From: Arnd Bergmann <arnd@...db.de>
To: David Howells <dhowells@...hat.com>
Cc: viro@...iv.linux.org.uk, smfrench@...il.com, jlayton@...hat.com,
mcao@...ibm.com, aneesh.kumar@...ux.vnet.ibm.com,
linux-cifs@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, samba-technical@...ts.samba.org,
sjayaraman@...e.de, linux-ext4@...r.kernel.org
Subject: Re: [PATCH 3/3] Add a pair of system calls to make extended file stats available [ver #2]
On Wednesday 30 June 2010 10:55:51 David Howells wrote:
> Arnd Bergmann <arnd@...db.de> wrote:
>
> > I think it would be better to leave the structure as write-only from
> > the kernel
>
> Why?
Consistency mostly. stat and stat64 don't read it, so I think xstat
also shouldn't if we can easily avoid it.
It also makes things like strace more complicated.
> > and pass the query_flags and struct_version as syscall arguments, though it
> > makes sense to store them in the result as well.
>
> The problem with that is that the number of syscall arguments is limited, and
> there is no SYSCALL_DEFINE7.
>
> On the other hand, I could make a separate argument block struct and pass a
> pointer to it...
No, I think that would be worse than the current version. But if you remove
the structure version in favor of the flags, you only need six arguments
anyway.
You can also go further and fold the structure length into flags, because
the length is just a function of the data you are passing.
Having a system call with flags, size and version is like wearing a belt,
braces and suspenders. An unsigned long flags argument should be enough to
hold up your pants[1].
Arnd
[1] I hope I managed to make this sound wrong in both American and proper
English.
--
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