Re: [RHEL5 PATCH 2/4] VFS: Make inode numbers 64-bits

Al Viro <[email protected]> wrote:

> NAK.  There's no need to touch i_ino and a lot of reasons for not doing
> that.

Like all those printks that write ambiguous messages because they can't report
the full inode number?  I'm not so worried about those because they're for the
most part debugging messages, but still, they *can* report invalid information
because i_ino is not big enough in error and warning messages.

David
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • 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: Al Viro <[email protected]>

• References:
  • 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]>

• Prev by Date: Re: [RHEL5 PATCH 1/4] Provide fallback full 64-bit divide/modulus ops for gcc
• Next by Date: Re: [PATCH] ISDN: fix double free bug in isdn_net
• Previous by thread: Re: [RHEL5 PATCH 2/4] VFS: Make inode numbers 64-bits
• Next by thread: Re: [RHEL5 PATCH 2/4] VFS: Make inode numbers 64-bits
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]