| От | Stephen Frost |
|---|---|
| Тема | Re: Strange hanging bug in a simple milter |
| Дата | |
| Msg-id | 20130913164011.GR2706@tamriel.snowman.net обсуждение исходный текст |
| Ответ на | Re: Strange hanging bug in a simple milter (Stephen Frost <sfrost@snowman.net>) |
| Ответы |
Re: Strange hanging bug in a simple milter
|
| Список | pgsql-hackers |
Heikki, all,
* Stephen Frost (sfrost@snowman.net) wrote:
> Very curious. Out of time right now to look into it, but will probably
> be back at it later tonight.
Alright, I was back at this a bit today and decided to go with a hunch-
and it looks like I might have been right to try.
Leaving the locking callback hooks in place appears to prevent the
deadlocks from happening, at least with this little app.
IOW, in destroy_ssl_system(), simply arrange to not have
CRYPTO_set_locking_callback(NULL); and CRYPTO_set_id_callback(NULL);
called. I've done this with the very simple attached patch. Per the
comment above destroy_ssl_system(), this doesn't seem to be an
acceptable solution because libpq might get unloaded from the
application, but perhaps it points the way towards what the issue is.
My thought had been that there was an issue with regard to signal
handling, but I've been unable to confirm that, nor is it clear why that
would be the case. In any case, I'm curious what others think of these
results and if anyone can reproduce the deadlock with this patch
applied.
Thanks!
Stephen
В списке pgsql-hackers по дате отправления:
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера