public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: IA64 ino_t incorrectly sized?
Date: Thu, 09 Oct 2003 03:15:01 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106566948017524@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106378281914262@msgid-missing>

On Wed, Oct 08, 2003 at 06:57:13PM -0700, David Mosberger wrote:
> >>>>> On Thu, 9 Oct 2003 11:25:58 +1000, Nathan Scott <nathans@sgi.com> said:
> 
>   Nathan> The problem is not the interfaces - they tend to use "long"
>   Nathan> directly and will be unaffected.  When I started running our
>   Nathan> tests with large inode numbers, for the most part everything
>   Nathan> just worked.
> 
> Argh, of course it's about interfaces.  We don't want to break
> something unknowingly because of this change.

Yes, I understand that.

> Saying that "for the
> most part everything just worked" isn't exactly reassuring!

You have misunderstood and/or I have not been clear enough.

"When I started running tests"... i.e. before I fixed this issue
in asm-ia64/posix_types.h ... "for the most part everything just
worked"... i.e. most stuff worked before, but not the thing I
fixed; but now it is fixed, and all our tests pass now, and I
know of no remaining issues.

I did not review every possible interface for use of ino_t, no.
I suppose that needs to be done, I don't have that kind of time
available just now.

cheers.

-- 
Nathan

  parent reply	other threads:[~2003-10-09  3:15 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-17  7:10 IA64 ino_t incorrectly sized? Nathan Scott
2003-09-17 14:33 ` Jes Sorensen
2003-09-17 17:26 ` David Mosberger
2003-09-29  5:52 ` Nathan Scott
2003-10-08 23:51 ` David Mosberger
2003-10-09  1:25 ` Nathan Scott
2003-10-09  1:57 ` David Mosberger
2003-10-09  3:15 ` Nathan Scott [this message]
2003-10-09  3:53 ` David Mosberger
2003-10-09  4:55 ` Nathan Scott
2003-10-09 20:46 ` David Mosberger
2003-10-10  2:22 ` Nathan Scott
2003-10-15  1:25 ` Nathan Scott
2003-10-15  1:48 ` Andrew Morton
2003-10-15  4:47 ` David Mosberger
2003-10-15  5:18 ` Andrew Morton
2003-10-15  6:06 ` Nathan Scott
2003-10-15  6:16 ` Nathan Scott
2003-10-15  6:21 ` David Mosberger
2003-10-15  6:28 ` Andrew Morton
2003-10-15  6:34 ` Nathan Scott
2003-10-15 12:42 ` Andi Kleen
2003-10-15 12:54 ` Christoph Hellwig
2003-10-15 13:29 ` Matthew Wilcox
2003-10-15 13:40 ` Christoph Hellwig
2003-10-15 16:32 ` David Mosberger
2003-10-15 16:59 ` David Mosberger
2003-10-15 17:40 ` David Mosberger
2003-10-15 23:40 ` Neil Brown
2003-10-16  1:20 ` David Mosberger
2003-10-16 22:47 ` Nathan Scott
2003-10-17  0:47 ` Neil Brown
2003-10-17  1:56 ` Nathan Scott
2003-10-21  3:37 ` Neil Brown

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=marc-linux-ia64-106566948017524@msgid-missing \
    --to=nathans@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    /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