Re: [PATCH 1/3] make static counters in new_inode and iunique be 32 bits

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 <[email protected]>

Ok.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH 1/3] make static counters in new_inode and iunique be 32 bits
    • From: Jeff Layton <[email protected]>

• Prev by Date: Re: .version keeps being updated
• Next by Date: Re: [PATCH 2/3] change libfs sb creation routines to avoid collisions with their root inodes
• Previous by thread: [PATCH 1/3] make static counters in new_inode and iunique be 32 bits
• Next by thread: [PATCH 1/3] make static counters in new_inode and iunique be 32 bits
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]