Hi, On Thu, 1 Mar 2001, Alexander Viro wrote: > IOW, if it's worth doing at all it probably should be > on expanding path in vmtruncate() - limit checks are already > done, but old i_size is still not lost... The fs where it's important have mmu_private, that's what I use to decide whether to expand or truncate. bye, Roman - 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/
- Re: fat problem in 2.4.2 Alan Cox
- Re: fat problem in 2.4.2 Peter Daum
- [PATCH] Re: fat problem in 2.4.2 Alexander Viro
- Re: [PATCH] Re: fat problem in 2.4.2 Albert D. Cahalan
- Re: fat problem in 2.4.2 Alan Cox
- [CFT][PATCH] Re: fat problem in 2.4.2 Alexander Viro
- Re: [CFT][PATCH] Re: fat problem in 2.4... Linus Torvalds
- Re: [CFT][PATCH] Re: fat problem i... Chris Mason
- Re: [CFT][PATCH] Re: fat problem in 2.4... Roman Zippel
- Re: [CFT][PATCH] Re: fat problem i... Alexander Viro
- ftruncate not extending files? Roman Zippel
- ftruncate not extending files? bert hubert
- Re: ftruncate not extending files? Malcolm Beattie
- Re: ftruncate not extending files? Dmitry A. Fedorov
- Re: ftruncate not extending files? Hugh Dickins
- Re: ftruncate not extending fi... Kai Henningsen
- Re: ftruncate not extending files? Jens-Uwe Mager