On Tue, 15 Aug 2006 10:25:47 +0100 David Howells <[email protected]> wrote: > > Interestingly, one of these also touches userspace: /proc/locks passes the > inode number out, but will pass the wrong one if i_ino is too short. Does > anything in userspace actually use that? As far as I know, /proc/locks is just useful for debugging the locking code. -- Cheers, Stephen Rothwell [email protected] http://www.canb.auug.org.au/~sfr/
Attachment:
pgpvJP1pkGtzK.pgp
Description: PGP signature
- References:
- Re: [RHEL5 PATCH 2/4] VFS: Make inode numbers 64-bits
- From: Al Viro <[email protected]>
- Re: [RHEL5 PATCH 2/4] VFS: Make inode numbers 64-bits
- From: Al Viro <[email protected]>
- [PATCH 0/4] Use 64-bit inode numbers internally in the kernel
- From: David Howells <[email protected]>
- [RHEL5 PATCH 2/4] VFS: Make inode numbers 64-bits
- From: David Howells <[email protected]>
- Re: [RHEL5 PATCH 2/4] VFS: Make inode numbers 64-bits
- From: David Howells <[email protected]>
- Re: [RHEL5 PATCH 2/4] VFS: Make inode numbers 64-bits
- From: David Howells <[email protected]>
- Re: [RHEL5 PATCH 2/4] VFS: Make inode numbers 64-bits
- Prev by Date: Re: Daily crashes, incorrect RAID behaviour
- Next by Date: Re: Oops on suspend
- Previous by thread: Re: [RHEL5 PATCH 2/4] VFS: Make inode numbers 64-bits
- Next by thread: [RHEL5 PATCH 3/4] VFS: Clear up u-long-long ino_t print format warnings
- Index(es):
 |