Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

common: signal_handler: added support for using reentrant strsignal() implementations vs. sys_siglist[] #6796

Merged
merged 1 commit into from Dec 19, 2015

Conversation

dx9
Copy link
Contributor

@dx9 dx9 commented Dec 4, 2015

Hey @liewegas, I've rebased #6223. Not sure if I was suppose to open a new PR. Cheers

@dx9 dx9 changed the title signal_handler: fallback to strsignal when sys_siglist is not implemeted signal_handler: fallback to strsignal when sys_siglist is not implemented Dec 4, 2015
@dx9
Copy link
Contributor Author

dx9 commented Dec 4, 2015

The patch assumes that if sys_siglist does not exist strsignal() is safe.

@dx9 dx9 changed the title signal_handler: fallback to strsignal when sys_siglist is not implemented signal_handler: added support for using reentrant strsignal() implementations vs. sys_siglist[] Dec 7, 2015
…ntations vs. sys_siglist[]

musl libc does not provide sys_siglist. It does provide a reentrant implementation of strsignal().

Added a cmake build option for using reentrant strsignal() impls instead of sys_siglist.

Signed-off-by: John Coyle <dx9err@gmail.com>
@liewegas
Copy link
Member

lgtm

liewegas added a commit that referenced this pull request Dec 19, 2015
common: signal_handler: added support for using reentrant strsignal() implementations vs. sys_siglist[]

Reviewed-by: Sage Weil <sage@redhat.com>
@liewegas liewegas merged commit ae0dc47 into ceph:master Dec 19, 2015
@ghost ghost changed the title signal_handler: added support for using reentrant strsignal() implementations vs. sys_siglist[] common: signal_handler: added support for using reentrant strsignal() implementations vs. sys_siglist[] Feb 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants