Lines Matching +full:32 +full:bit
2 Notes on the change from 16-bit UIDs to 32-bit UIDs
15 What's left to be done for 32-bit UIDs on all Linux architectures:
22 properly with huge UIDs. If it can deal with 64-bit file offsets on all
27 (currently, the old 16-bit UID and GID are still written to disk, and
28 part of the former pad space is used to store separate 32-bit UID and
31 - Need to validate that OS emulation calls the 16-bit UID
32 compatibility syscalls, if the OS being emulated used 16-bit UIDs, or
33 uses the 32-bit UID system calls properly otherwise.
40 (need to support whatever new 32-bit UID system calls are added to
45 At present, 32-bit UIDs _should_ work for:
59 Filesystems with simple fixups to prevent 16-bit UID wraparound:
67 - The ncpfs and smpfs filesystems cannot presently use 32-bit UIDs in
68 all ioctl()s. Some new ioctl()s have been added with 32-bit UIDs, but
71 - The ELF core dump format only supports 16-bit UIDs on arm, i386, m68k,
76 16-bit UIDs on arm, i386, m68k, sh, and sparc32.
79 (it should be safe because it's always used a 32-bit integer to