Re: [PATCH 0/3] ensure unique i_ino in filesystems without permanent inode numbers (introduction)

Jeff Layton wrote:
> Apologies for the long email, but I couldn't come up with a way to explain
> this in fewer words. Many filesystems that are part of the linux kernel
> have problems with how they have assign out i_ino values:
>

If there are no further comments/suggestions on this patchset, I'd like to
ask Andrew to add it to -mm soon and target getting it rolled into 2.6.21.
Once it's in -mm, I'll start posting more patches to convert the other
filesystems.

Andrew, are the patches I've already posted sufficient, or should I resend
the set?

Thanks,
Jeff

-
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/

Follow-Ups:
- Re: [PATCH 0/3] ensure unique i_ino in filesystems without permanent inode numbers (introduction)
  - From: Jörn Engel <[email protected]>

References:
- [PATCH 0/3] ensure unique i_ino in filesystems without permanent inode numbers (introduction)
  - From: Jeff Layton <[email protected]>

Prev by Date: Re: realtime-preempt and arm
Next by Date: Re: [ANNOUNCE] RAIF: Redundant Array of Independent Filesystems
Previous by thread: [PATCH 0/3] ensure unique i_ino in filesystems without permanent inode numbers (introduction)
Next by thread: Re: [PATCH 0/3] ensure unique i_ino in filesystems without permanent inode numbers (introduction)
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]