Searched hist:"2116271 a347d1181b5497602c2bfada1de8fd53b" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/fs/nfs/ |
| H A D | proc.c | diff 2116271a347d1181b5497602c2bfada1de8fd53b Tue May 20 18:34:39 CDT 2008 Trond Myklebust <Trond.Myklebust@netapp.com> NFS: Add correct bounds checking to NFSv2 locks
NFSv2 file locking currently fails the Connectathon tests, because the
calls to the VFS locking code do not return an EINVAL error if the
struct file_lock overflows the 32-bit boundaries.
The problem is due to the fact that we occasionally call helpers from
fs/locks.c in order to avoid RPC calls to the server when we know that a
local process holds the lock. These helpers are, of course, always
64-bit enabled, so EINVAL is not returned in cases when it would if
the call had gone to the NLM code.
For consistency, we therefore add support for a bounds-checking helper.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
|
| H A D | file.c | diff 2116271a347d1181b5497602c2bfada1de8fd53b Tue May 20 18:34:39 CDT 2008 Trond Myklebust <Trond.Myklebust@netapp.com> NFS: Add correct bounds checking to NFSv2 locks
NFSv2 file locking currently fails the Connectathon tests, because the
calls to the VFS locking code do not return an EINVAL error if the
struct file_lock overflows the 32-bit boundaries.
The problem is due to the fact that we occasionally call helpers from
fs/locks.c in order to avoid RPC calls to the server when we know that a
local process holds the lock. These helpers are, of course, always
64-bit enabled, so EINVAL is not returned in cases when it would if
the call had gone to the NLM code.
For consistency, we therefore add support for a bounds-checking helper.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
|
| /openbmc/linux/include/linux/ |
| H A D | nfs_xdr.h | diff 2116271a347d1181b5497602c2bfada1de8fd53b Tue May 20 18:34:39 CDT 2008 Trond Myklebust <Trond.Myklebust@netapp.com> NFS: Add correct bounds checking to NFSv2 locks
NFSv2 file locking currently fails the Connectathon tests, because the
calls to the VFS locking code do not return an EINVAL error if the
struct file_lock overflows the 32-bit boundaries.
The problem is due to the fact that we occasionally call helpers from
fs/locks.c in order to avoid RPC calls to the server when we know that a
local process holds the lock. These helpers are, of course, always
64-bit enabled, so EINVAL is not returned in cases when it would if
the call had gone to the NLM code.
For consistency, we therefore add support for a bounds-checking helper.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
|