path: root/
diff options
authorNiels de Vos <>2017-07-17 16:45:47 +0200
committerShyamsundar Ranganathan <>2017-07-21 15:03:29 +0000
commitbec1c177d7fccaa6dbe353cb06064256bc997895 (patch)
treeacdafcec3538e4268e26797f1f63d0506ec031a3 /
parent52725e305d39296a7d01944c62c3166a3cad06bc (diff)
nfs/nlm: keep track of the call-state and frame for notifications
When blocking locks are used, a new frame is allocated that is used to send the notification to the client once once the lock becomes available. In all other cases, the frame that contains the request from the client will be used for the reply. Because there was no way to track the different clients with their requests (captured in the call-state), the call-state could be free'd before the notification was sent to the client. This caused a use-after-free of the call-state and could trigger segfaults of the Gluster/NFS server or incorrect replies on (un)lock requests. By introducing a nlm4_notify_args structure, the call-state and frame can be tracked better. This prevents the possibility of segfaulting when the call-state is used after being free'd. Cherry picked from commit b81997264f079983fa02bd5fa2b3715224942b00: > BUG: 1467313 > Change-Id: I285d2bc552f509e5145653b7a50afcff827cd612 > Signed-off-by: Niels de Vos <> > Reviewed-on: > Smoke: Gluster Build System <> > CentOS-regression: Gluster Build System <> > Reviewed-by: Kaleb KEITHLEY <> > Reviewed-by: jiffin tony Thottan <> Change-Id: I285d2bc552f509e5145653b7a50afcff827cd612 BUG: 1471869 Signed-off-by: Niels de Vos <> Reviewed-on: CentOS-regression: Gluster Build System <> Smoke: Gluster Build System <> Reviewed-by: Shyamsundar Ranganathan <>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions