All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: IA64 ino_t incorrectly sized?
Date: Wed, 08 Oct 2003 23:51:09 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106565735509526@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106378281914262@msgid-missing>

>>>>> On Mon, 29 Sep 2003 15:52:56 +1000, Nathan Scott <nathans@sgi.com> said:

  >>  Extending ino_t to 64 bits came up last October [1].  AFAIK,
  >> nobody bothered to investigate & send a patch, so things didn't
  >> change since then.

  >> --david

  >> [1] http://www.gelato.unsw.edu.au/linux-ia64/0210/3952.html


  Nathan> I notice a big batch of IA64 changes has just gone into
  Nathan> 2.6-test6, but this change seems to be missing.  Is it in
  Nathan> someones queue for next time or do I need to describe the
  Nathan> problem more clearly?

  Nathan> The investigation and the patch I sent are available
  Nathan> here[2].

  Nathan> cheers.

  Nathan> -- Nathan

  Nathan> [2] http://www.gelato.unsw.edu.au/linux-ia64/0309/6681.html

The mail you're referring to talks about getdents64() only.  What I
didn't see is an argument why this is the _only_ user visible
interface that might be affected.  Are there any other interfaces
(syscalls, /proc/whatever, etc.) that may directly or indirectly be
affected?  If not and if the change has been run through a reasonable
test-suite (LTP?) without ill effects, I'm certainly OK with the
change.

	--david

PS: It would help to get this resolved quickly, e.g., before test8.

  parent reply	other threads:[~2003-10-08 23:51 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 [this message]
2003-10-09  1:25 ` Nathan Scott
2003-10-09  1:57 ` David Mosberger
2003-10-09  3:15 ` Nathan Scott
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-106565735509526@msgid-missing \
    --to=davidm@napali.hpl.hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.