Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 09 May 2014 09:28:29 +0100
From:      Karl Pielorz <kpielorz_lst@tdx.co.uk>
To:        Konstantin Belousov <kostikbel@gmail.com>, Daniel Eischen <deischen@freebsd.org>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: Stuck CLOSED sockets / sshd / zombies...
Message-ID:  <45E85B0B7769CBE623165498@Mail-PC.tdx.co.uk>
In-Reply-To: <20140411183949.GX21331@kib.kiev.ua>
References:  <20140409111917.GH21331@kib.kiev.ua> <851413886E3982D2CCFEA9D9@Mail-PC.tdx.co.uk> <20140410184855.GP21331@kib.kiev.ua> <211BD03C086DDB1A07FDF036@Mail-PC.tdx.co.uk> <20140411131649.GR21331@kib.kiev.ua> <652B8CA4866C0B9E4650430B@Mail-PC.tdx.co.uk> <20140411141526.GT21331@kib.kiev.ua> <464979E8F6FCBD7EA7DAA38B@Mail-PC.tdx.co.uk> <20140411160628.GV21331@kib.kiev.ua> <Pine.GSO.4.64.1404111320250.23129@sea.ntplx.net> <20140411183949.GX21331@kib.kiev.ua>

next in thread | previous in thread | raw e-mail | index | archive | help

--On 11 April 2014 21:39 +0300 Konstantin Belousov <kostikbel@gmail.com> 
wrote:

> BTW, below is the updated patch with the workaround for sshd issue.
>
> diff --git a/secure/usr.sbin/sshd/Makefile b/secure/usr.sbin/sshd/Makefile
> index 4f730a9..b3231a4 100644
> --- a/secure/usr.sbin/sshd/Makefile
> +++ b/secure/usr.sbin/sshd/Makefile
> @@ -57,6 +57,12 @@ CFLAGS+= -DNONE_CIPHER_ENABLED
>  DPADD+= ${LIBCRYPT} ${LIBCRYPTO} ${LIBZ}
>  LDADD+= -lcrypt -lcrypto -lz
>
> +# put the threading library last
> +.if ${MK_KERBEROS_SUPPORT} != "no"
> +DPADD+= ${LIBPTHREAD}
> +LDADD+= -lpthread
> +.endif
> +
>  .if defined(LOCALBASE)
>  CFLAGS+= -DXAUTH_PATH=\"${LOCALBASE}/bin/xauth\"
>  .endif

As far as I can see this hasn't been committed to 10/Stable yet? (or 
anywhere?) That means anything we build from 10/Stable is still going to 
have this issue - where sshd hangs because "libthr wrapper thr_sighandler() 
for the signal handlers is not installed as the recepient of the kernel 
signal, which prevents libthr locks for rtld from working properly."

This is causing us issues [as well as some other people running other tools 
- not fixed by this patch] - I would raise a PR - but it's not my patch! :)

Thanks,

-Karl
 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45E85B0B7769CBE623165498>