Re: [REVIEW] Prevent direct I/O from mapping extents beyond eof | |
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] | |
On Fri, Aug 15, 2008 at 03:27:56PM -0700, Andrew Morton wrote: > Oh gee, I forget, and so many people have done drivebys on that code... > > We _could_ add additional i_size checking into direct-io.c but bear in > mind that it would be best-effort unreliable stuff. The code will > still be tripped up by concurrent extends and concurrent truncates. > > So we'll still end up calling the fs for blocks outside i_size, only > less commonly. I think. Yeah, guess we should put in this patch then. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
[Site Home] [Kernel Newbies] [UNIX Filesystems] [Share Photos] [Security] [Netfilter] [Bugtraq] [Rubini] [Photo] [Yosemite] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Ext4 Filesystem] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Video 4 Linux] [Device Mapper] [Linux Resources]
![]() |