ssp: Protect sig2str with proper visibility markers
We only define SIG2STR_MAX with careful visibility, but define the
fortified version unconditionally. It needs to have the same visibility
both places.
Fixes: 3d12567133
Reviewed by: jrtc27, kevans
Sponsored by: Netflix
This commit is contained in:
@@ -35,6 +35,7 @@
|
||||
|
||||
__BEGIN_DECLS
|
||||
|
||||
#if __POSIX_VISIBLE >= 202405 || __BSD_VISIBLE
|
||||
__ssp_redirect_raw_impl(int, sig2str, sig2str,
|
||||
(int signum, char *__restrict str))
|
||||
{
|
||||
@@ -43,6 +44,7 @@ __ssp_redirect_raw_impl(int, sig2str, sig2str,
|
||||
|
||||
return (__ssp_real(sig2str)(signum, str));
|
||||
}
|
||||
#endif
|
||||
|
||||
__END_DECLS
|
||||
|
||||
|
||||
Reference in New Issue
Block a user