diff options
author | David Jeffery <djeffery@redhat.com> | 2013-07-10 13:19:50 -0400 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2013-07-28 16:18:48 -0700 |
commit | a00c4c9f176094d7b71acd410f871b609f5e7c84 (patch) | |
tree | 3f55b6c425c57429f771fc7f230116f22bd5cead /kernel/trace | |
parent | 101e49a9ce6fadd876ae68bddf6f155bbd02a776 (diff) | |
download | kernel_samsung_espresso10-a00c4c9f176094d7b71acd410f871b609f5e7c84.zip kernel_samsung_espresso10-a00c4c9f176094d7b71acd410f871b609f5e7c84.tar.gz kernel_samsung_espresso10-a00c4c9f176094d7b71acd410f871b609f5e7c84.tar.bz2 |
lockd: protect nlm_blocked access in nlmsvc_retry_blocked
commit 1c327d962fc420aea046c16215a552710bde8231 upstream.
In nlmsvc_retry_blocked, the check that the list is non-empty and acquiring
the pointer of the first entry is unprotected by any lock. This allows a rare
race condition when there is only one entry on the list. A function such as
nlmsvc_grant_callback() can be called, which will temporarily remove the entry
from the list. Between the list_empty() and list_entry(),the list may become
empty, causing an invalid pointer to be used as an nlm_block, leading to a
possible crash.
This patch adds the nlm_block_lock around these calls to prevent concurrent
use of the nlm_blocked list.
This was a regression introduced by
f904be9cc77f361d37d71468b13ff3d1a1823dea "lockd: Mostly remove BKL from
the server".
Signed-off-by: David Jeffery <djeffery@redhat.com>
Cc: Bryan Schumaker <bjschuma@netapp.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'kernel/trace')
0 files changed, 0 insertions, 0 deletions