On Tue, 2011-10-25 at 22:11 +0200, Jakub Hrozek wrote:
On Tue, Oct 25, 2011 at 03:25:35PM -0400, Stephen Gallagher wrote:
> There are several places (all error-handling) where sss_cmd_done()
> is called with no response packet created. As a short-term
> solution, we need to check whether the packet is NULL and simply
> return EINVAL. client_send() (the consumer) will then forcibly
> disconnect the client (which will return PAM_SYSTEM_ERR to the
> client).
>
> This is a quick fix for
>
https://bugzilla.redhat.com/show_bug.cgi?id=748924
>
> We don't have enough information (or steps to reproduce) to trace back
> the processing to its origin, so the best thing we can do for the moment
> is to simply prevent the crash. The client will receive an error, but
> the SSSD will continue to function.
Ack
would it make sense to add a loud DEBUG() debug message so we are notified
when this hits again?
Pushed to master, sssd-1-6 and sssd-1-5.