diff options
author | Elena Reshetova <elena.reshetova@intel.com> | 2017-10-20 12:53:37 +0300 |
---|---|---|
committer | Anna Schumaker <Anna.Schumaker@Netapp.com> | 2017-11-17 13:48:01 -0500 |
commit | 2f62b5aa4814be2c511553fd6afb4d35b6c2503b (patch) | |
tree | cf402bfd8d23ea6dbf02e67a45edd9e49a8822af /fs/nfs/nfs4client.c | |
parent | 194bc1f48100a3b6fbd50d7a2218b594f0c564b6 (diff) | |
download | linux-2f62b5aa4814be2c511553fd6afb4d35b6c2503b.tar.gz linux-2f62b5aa4814be2c511553fd6afb4d35b6c2503b.tar.bz2 linux-2f62b5aa4814be2c511553fd6afb4d35b6c2503b.zip |
fs, nfs: convert nfs_lock_context.count from atomic_t to refcount_t
atomic_t variables are currently used to implement reference
counters with the following properties:
- counter is initialized to 1 using atomic_set()
- a resource is freed upon counter reaching zero
- once counter reaches zero, its further
increments aren't allowed
- counter schema uses basic atomic operations
(set, inc, inc_not_zero, dec_and_test, etc.)
Such atomic variables should be converted to a newly provided
refcount_t type and API that prevents accidental counter overflows
and underflows. This is important since overflows and underflows
can lead to use-after-free situation and be exploitable.
The variable nfs_lock_context.count is used as pure reference counter.
Convert it to refcount_t and fix up the operations.
Suggested-by: Kees Cook <keescook@chromium.org>
Reviewed-by: David Windsor <dwindsor@gmail.com>
Reviewed-by: Hans Liljestrand <ishkamiel@gmail.com>
Signed-off-by: Elena Reshetova <elena.reshetova@intel.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Diffstat (limited to 'fs/nfs/nfs4client.c')
0 files changed, 0 insertions, 0 deletions