[RFC] rgw: Libcurl+NSS memory leak mitigation when performing keystone SSL auth

[mkogan1]

Tracker issue:
http://tracker.ceph.com/issues/23375

When libcurl is configured with --with-nss
There is a memory leak in the PK11_CreateGenericObject() function (in libnss3.so)
that occurs when keystone users authority authentication is using ssl.
(rgw_keystone_verify_ssl = true)

By calling the curl_global_cleanup() its possible to release the memory in libcurl.

(This patch is currently only for the curl_easy_* flow, can be extended to the curl_multi_* flow also)

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you are a maintainer or core committer, please follow-up on this issue to identify what steps should be taken by the author to move this proposed change forward.
If you are the author of this pull request, thank you for your proposed contribution. If you believe this change is still appropriate, please ensure that any feedback has been addressed and ask for a code review.

[mattbenjamin]

@mkogan1 could this get a rebase?

[mattbenjamin]

@cbodley and I discussed--maybe the way forward here is to globally transition out of NSS crypto?

[mattbenjamin]

@liewegas ^^

[liewegas]

IIRC @rzarzynski said the backport is nontrivial, but it brings along some performance benefits with it. If it's feasible it seems like a better cost/benefit than spending time fixing old nss code.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you are a maintainer or core committer, please follow-up on this issue to identify what steps should be taken by the author to move this proposed change forward.
If you are the author of this pull request, thank you for your proposed contribution. If you believe this change is still appropriate, please ensure that any feedback has been addressed and ask for a code review.

[stale]

This pull request has been automatically closed because there has been no activity for 90 days. Please feel free to reopen this pull request (or open a new one) if the proposed change is still appropriate. Thank you for your contribution!