Al Viro <viro@xxxxxxxxxxxxxxxx> 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-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
