Searched hist:"1841 b9b61492e35234bdca8a5737a0e5df770f27" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/fs/nfsd/ |
| H A D | xdr.h | diff 1841b9b61492e35234bdca8a5737a0e5df770f27 Thu Oct 01 17:59:44 CDT 2020 Chuck Lever <chuck.lever@oracle.com> NFSD: Fix .pc_release method for NFSv2
nfsd_release_fhandle() assumes that rqstp->rq_resp always points to
an nfsd_fhandle struct. In fact, no NFSv2 procedure uses struct
nfsd_fhandle as its response structure.
So far that has been "safe" to do because the res structs put the
resp->fh field at that same offset as struct nfsd_fhandle. I don't
think that's a guarantee, though, and there is certainly nothing
preventing a developer from altering the fields in those structures.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
|
| H A D | nfsxdr.c | diff 1841b9b61492e35234bdca8a5737a0e5df770f27 Thu Oct 01 17:59:44 CDT 2020 Chuck Lever <chuck.lever@oracle.com> NFSD: Fix .pc_release method for NFSv2
nfsd_release_fhandle() assumes that rqstp->rq_resp always points to
an nfsd_fhandle struct. In fact, no NFSv2 procedure uses struct
nfsd_fhandle as its response structure.
So far that has been "safe" to do because the res structs put the
resp->fh field at that same offset as struct nfsd_fhandle. I don't
think that's a guarantee, though, and there is certainly nothing
preventing a developer from altering the fields in those structures.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
|
| H A D | nfsproc.c | diff 1841b9b61492e35234bdca8a5737a0e5df770f27 Thu Oct 01 17:59:44 CDT 2020 Chuck Lever <chuck.lever@oracle.com> NFSD: Fix .pc_release method for NFSv2
nfsd_release_fhandle() assumes that rqstp->rq_resp always points to
an nfsd_fhandle struct. In fact, no NFSv2 procedure uses struct
nfsd_fhandle as its response structure.
So far that has been "safe" to do because the res structs put the
resp->fh field at that same offset as struct nfsd_fhandle. I don't
think that's a guarantee, though, and there is certainly nothing
preventing a developer from altering the fields in those structures.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
|