From lmb@cloudflare.com Thu Oct 20 08:57:10 2016 From: lmb@cloudflare.com To: openldap-bugs@openldap.org Subject: Re: (ITS#8504) LDMB: Return EPIPE from mdb_env_copyfd2 instead abort on SIGPIPE Date: Thu, 20 Oct 2016 08:57:08 +0000 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2244775676777604982==" --===============2244775676777604982== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit --001a114741aec1bad3053f481b06 Content-Type: text/plain; charset=UTF-8 On 20 October 2016 at 09:35, Hallvard Breien Furuseth < h.b.furuseth(a)usit.uio.no> wrote: > > Hmm. Nevermind, it's probably better to leave that to the user. > It gets ugly for a library to meddle with the current thread's > signals. I.e. it must check if SIGPIPE was already pending > before the call, and don't collect it on EPIPE in that case. > Yeah, I agree. Your changes LGTM. Interesting point re atomic int write, I wasn't entirely sure how mc_error could be accesses, so I decided to play it safe. -- Lorenz Bauer | Systems Engineer 25 Lavington St., London SE1 0NZ www.cloudflare.com --001a114741aec1bad3053f481b06 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 20 October 2016 at 09:35, Hallvard Breien Furuseth <= ;h.b.furuseth= @usit.uio.no> wrote:
Hmm.=C2=A0 Nevermind, it's probably better to leave that to the user. It gets ugly for a library to meddle with the current thread's
signals.=C2=A0 I.e. it must check if SIGPIPE was already pending
before the call, and don't collect it on EPIPE in that case.

Yeah, I agree. Your changes LGTM.

Interesting point re atomic int write, I wasn't entirely sure how mc_= error could be accesses, so I decided to play it safe.

= --
Lo= renz Bauer =C2=A0| =C2=A0Systems Engineer
25 Lavington St., London SE1 0= NZ

www.cloud= flare.com
--001a114741aec1bad3053f481b06-- --===============2244775676777604982==--