aboutsummaryrefslogtreecommitdiffstats
path: root/security
diff options
context:
space:
mode:
authorJ. Bruce Fields <bfields@redhat.com>2011-06-29 16:49:04 -0400
committerGreg Kroah-Hartman <gregkh@suse.de>2011-08-04 21:58:40 -0700
commit83d20a07d3fc171d5d7cddb6ebe2cd7a5fee1047 (patch)
treef44cd1bd71d6a3d81645a806fda0876033d53407 /security
parent4beae54c192e6f1dee12b70e205b800fd99d1fc7 (diff)
downloadkernel_samsung_espresso10-83d20a07d3fc171d5d7cddb6ebe2cd7a5fee1047.tar.gz
kernel_samsung_espresso10-83d20a07d3fc171d5d7cddb6ebe2cd7a5fee1047.tar.bz2
kernel_samsung_espresso10-83d20a07d3fc171d5d7cddb6ebe2cd7a5fee1047.zip
svcrpc: fix list-corrupting race on nfsd shutdown
commit ebc63e531cc6a457595dd110b07ac530eae788c3 upstream. After commit 3262c816a3d7fb1eaabce633caa317887ed549ae "[PATCH] knfsd: split svc_serv into pools", svc_delete_xprt (then svc_delete_socket) no longer removed its xpt_ready (then sk_ready) field from whatever list it was on, noting that there was no point since the whole list was about to be destroyed anyway. That was mostly true, but forgot that a few svc_xprt_enqueue()'s might still be hanging around playing with the about-to-be-destroyed list, and could get themselves into trouble writing to freed memory if we left this xprt on the list after freeing it. (This is actually functionally identical to a patch made first by Ben Greear, but with more comments.) Cc: gnb@fmeh.org Reported-by: Ben Greear <greearb@candelatech.com> Tested-by: Ben Greear <greearb@candelatech.com> Signed-off-by: J. Bruce Fields <bfields@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions