| commit | 8ef2ce3e16d9bec6cf015207c1c82a5b864046ac | |
| author | Bryan Schumaker <bjschuma@netapp.com> | |
| Wed, 23 Mar 2011 19:04:31 +0000 (23 15:04 -0400) | ||
| committer | Trond Myklebust <Trond.Myklebust@netapp.com> | |
| Wed, 23 Mar 2011 19:14:27 +0000 (23 15:14 -0400) | ||
| tree | 35441fd695c4f5215ab0061d8df26b4cfd9a44f5 | treesnapshot (tar.gz zip) |
| parent | 480c2006ebb44ae03165695db7b3e38c04e0d102 | commitdiff |
NFS: Detect loops in a readdir due to bad cookies
Some filesystems (such as ext4) can return the same cookie value for
multiple files. If we try to start a readdir with one of these cookies,
the server will return the first file found with a cookie of the same
value. This can cause the client to enter an infinite loop.
Signed-off-by: Bryan Schumaker <bjschuma@netapp.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Some filesystems (such as ext4) can return the same cookie value for
multiple files. If we try to start a readdir with one of these cookies,
the server will return the first file found with a cookie of the same
value. This can cause the client to enter an infinite loop.
Signed-off-by: Bryan Schumaker <bjschuma@netapp.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
| fs/nfs/dir.c | diffblobblamehistory | |
| include/linux/nfs_fs.h | diffblobblamehistory |