All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	esandeen@redhat.com, aviro@redhat.com
Subject: Re: [PATCH 1/3] make static counters in new_inode and iunique be 32 bits
Date: Wed, 10 Jan 2007 21:21:03 +0000	[thread overview]
Message-ID: <20070110212103.GA4425@infradead.org> (raw)
In-Reply-To: <200701082047.l08Kl7mh001917@dantu.rdu.redhat.com>

On Mon, Jan 08, 2007 at 03:47:07PM -0500, Jeff Layton wrote:
> When a 32-bit program that was not compiled with large file offsets does a
> stat and gets a st_ino value back that won't fit in the 32 bit field, glibc
> (correctly) generates an EOVERFLOW error. We can't do anything about fs's
> with larger permanent inode numbers, but when we generate them on the fly,
> we ought to try and have them fit within a 32 bit field.
> 
> This patch takes the first step toward this by making the static counters in
> these two functions be 32 bits.
> 
> Signed-off-by: Jeff Layton <jlayton@redhat.com>

Ok.

  reply	other threads:[~2007-01-10 21:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-08 20:47 [PATCH 1/3] make static counters in new_inode and iunique be 32 bits Jeff Layton
2007-01-10 21:21 ` Christoph Hellwig [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-01-16 18:57 Jeff Layton
2006-12-29 19:11 Jeff Layton
2007-01-26 12:42 ` Kirill Korotaev

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=20070110212103.GA4425@infradead.org \
    --to=hch@infradead.org \
    --cc=aviro@redhat.com \
    --cc=esandeen@redhat.com \
    --cc=jlayton@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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.