[lkml]   [2006]   [Aug]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [RHEL5 PATCH 2/4] VFS: Make inode numbers 64-bits
    On Tue, Aug 15, 2006 at 09:32:57AM +0100, David Howells wrote:
    > Al Viro <> 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.

    In fs-independent code? How many of those do we actually have?
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-08-15 11:05    [W:0.018 / U:33.868 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site