| Subject: | Re: XFS bug with ftruncate, mmap and holes. |
|---|---|
| From: | Andrew Morton <akpm@xxxxxxxxxx> |
| Date: | Mon, 28 Jan 2002 14:49:13 -0800 |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
Ethan Benson wrote: > > someone i was talking to recently has been using the 2.4.17 xfs > patches with 2.4.18pre kernels and found apt-get failed due to errors > returned by msync() (which appears to be returning 1 (not -1)). > msync is involved in writing these apt binary cache files. > Interesting. In 2.4.18-pre3 I changed msync. Previously, it was ignoring things like EIO and ENOSPC on writepage() operations. The change was to correctly propagate these error codes all the way back to the caller, all over the place. The raw diff is at http://www.zip.com.au/~akpm/linux/2.4/2.4.18-pre3/msync-ret.patch If someone is returning `1' from msync() then probably an underlying filesystem is returning `1' from its get_block() or writepage() method. It shouldn't. It should return either zero or a negative errno. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: mkfs on large h/w RAID fails, Wessel Dankers |
|---|---|
| Next by Date: | [no subject], Russell Cattelan |
| Previous by Thread: | Re: XFS bug with ftruncate, mmap and holes., Steve Lord |
| Next by Thread: | Re: XFS bug with ftruncate, mmap and holes., Steve Lord |
| Indexes: | [Date] [Thread] [Top] [All Lists] |