diff options
author | Christoph Hellwig <hch@infradead.org> | 2009-01-08 14:00:00 -0500 |
---|---|---|
committer | Lachlan McIlroy <lachlan@redback.melbourne.sgi.com> | 2009-01-09 16:18:24 +1100 |
commit | 15440319767942a363f282d6585303d3d75088ba (patch) | |
tree | 9b7e64cba3989d78561b5c4e37544790f8cf5ba5 /samples/kobject | |
parent | e6edbd1c1cbef278d58cdd8b046599ba8ac90cfc (diff) | |
download | kernel_samsung_aries-15440319767942a363f282d6585303d3d75088ba.zip kernel_samsung_aries-15440319767942a363f282d6585303d3d75088ba.tar.gz kernel_samsung_aries-15440319767942a363f282d6585303d3d75088ba.tar.bz2 |
[XFS] truncate readdir offsets to signed 32 bit values
John Stanley reported EOVERFLOW errors in readdir from his self-build
glibc. I traced this down to glibc enabling d_off overflow checks
in one of the about five million different getdents implementations.
In 2.6.28 Dave Woodhouse moved our readdir double buffering required
for NFS4 readdirplus into nfsd and at that point we lost the capping
of the directory offsets to 32 bit signed values. Johns glibc used
getdents64 to even implement readdir for normal 32 bit offset dirents,
and failed with EOVERFLOW only if this happens on the first dirent in
a getdents call. I managed to come up with a testcase that uses
raw getdents and does the EOVERFLOW check manually. We always hit
it with our last entry due to the special end of directory marker.
The patch below is a dumb version of just putting back the masking,
to make sure we have the same behavior as in 2.6.27 and earlier.
I will work on a better and cleaner fix for 2.6.30.
Reported-by: John Stanley <jpsinthemix@verizon.net>
Tested-by: John Stanley <jpsinthemix@verizon.net>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Dave Chinner <david@fromorbit.com>
Signed-off-by: Lachlan McIlroy <lachlan@sgi.com>
Diffstat (limited to 'samples/kobject')
0 files changed, 0 insertions, 0 deletions