Thread (14 messages) 14 messages, 5 authors, 2012-12-21

Re: new architectures, time_t __kernel_long_t

From: Al Viro <viro@ZenIV.linux.org.uk>
Date: 2012-12-21 05:02:11
Also in: lkml

On Thu, Dec 20, 2012 at 09:00:27PM -0800, H. Peter Anvin wrote:
On 12/20/2012 08:57 PM, Al Viro wrote:
quoted
On Wed, Nov 14, 2012 at 12:18:01PM +0000, Arnd Bergmann wrote:
quoted
The other types that are used as 64 bit on x32 are ino_t, nlink_t,
size_t, ssize_t, ptrdiff_t, and off_t.
*Kernel-side* we should not give a damn about the userland nlink_t, period.
Making it architecture-dependent had been a bad mistake that essentially
made nlink_t useless for the kernel.  That mistake had been fixed; please,
do not bring it back.  If some userland structure needs to include a field
encoding nlink_t values, please use an explicitly-sized type when refering
to it kernel-side.
We should never use userland types per se.  We can use __kernel_*_t
typedefs to make the kernel headers neater if it makes sense, but that
is often not even necessary.
... as long as we do not have typedef __kernel_foo_t foo_t in linux/types.h.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help