From: David Howells <dhowells@redhat.com>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: David Howells <dhowells@redhat.com>,
torvalds@osdl.org, akpm@osdl.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [RHEL5 PATCH 2/4] VFS: Make inode numbers 64-bits
Date: Tue, 15 Aug 2006 09:32:57 +0100 [thread overview]
Message-ID: <7619.1155630777@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <20060815013114.GS29920@ftp.linux.org.uk>
Al Viro <viro@ftp.linux.org.uk> 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
next prev parent reply other threads:[~2006-08-15 8:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <625fc13d0608141736q50dea86dh94cdf4ef19fe56d9@mail.gmail.com>
[not found] ` <20060814211504.27190.10491.stgit@warthog.cambridge.redhat.com>
[not found] ` <20060814211509.27190.51352.stgit@warthog.cambridge.redhat.com>
2006-08-15 1:31 ` [RHEL5 PATCH 2/4] VFS: Make inode numbers 64-bits Al Viro
2006-08-15 8:21 ` David Howells
2006-08-15 9:06 ` Al Viro
2006-08-15 8:32 ` David Howells [this message]
2006-08-15 9:02 ` Al Viro
2006-08-15 9:25 ` David Howells
2006-08-15 12:45 ` Stephen Rothwell
[not found] ` <7329.1155630113@warthog.cambridge.redhat.com>
2006-08-15 9:13 ` [PATCH 0/4] Use 64-bit inode numbers internally in the kernel Al Viro
2006-08-15 6:57 [RHEL5 PATCH 2/4] VFS: Make inode numbers 64-bits Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7619.1155630777@warthog.cambridge.redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=viro@ftp.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).