summaryrefslogtreecommitdiff
path: root/src/responder/nss/nsssrv_cmd.c
diff options
context:
space:
mode:
authorPavel Březina <pbrezina@redhat.com>2012-10-02 15:22:32 +0200
committerJakub Hrozek <jhrozek@redhat.com>2012-10-11 12:24:54 +0200
commit20ae5925d2963937dfc6a66017c05bb018cedd3f (patch)
tree4bf2d70afa531e0484efd1c476020c0a299e9c2f /src/responder/nss/nsssrv_cmd.c
parent6b45f632759293fc9f2a28317fae2e224ac53020 (diff)
downloadsssd-20ae5925d2963937dfc6a66017c05bb018cedd3f.tar.gz
sssd-20ae5925d2963937dfc6a66017c05bb018cedd3f.tar.bz2
sssd-20ae5925d2963937dfc6a66017c05bb018cedd3f.zip
do not call dp callbacks when responder is shutting down
https://fedorahosted.org/sssd/ticket/1514 We were experiencing crash duting responder shut down. This happened when there were some unresolved dp request during the shut down. The memory hierarchy is main_ctx->specific_ctx->rctx, where specific_ctx may be one of the pam, nss, sudo, etc. contexts. If we try to call dp request callback as a result of responder termination, the specific context is already semi freed, which may cause crash.
Diffstat (limited to 'src/responder/nss/nsssrv_cmd.c')
0 files changed, 0 insertions, 0 deletions