From owner-freebsd-bugs@freebsd.org  Fri May 12 10:34:59 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 31DE9D66F9B
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Fri, 12 May 2017 10:34:59 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 219021712
 for <freebsd-bugs@FreeBSD.org>; Fri, 12 May 2017 10:34:59 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4CAYwPb044233
 for <freebsd-bugs@FreeBSD.org>; Fri, 12 May 2017 10:34:59 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 219228] EINTR on thread with full signal mask.
Date: Fri, 12 May 2017 10:34:59 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.3-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: kib@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-219228-8-OBrqWPA9W2@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-219228-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-219228-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 May 2017 10:34:59 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219228

--- Comment #2 from Konstantin Belousov <kib@FreeBSD.org> ---
(In reply to Duane from comment #1)
I agree with your analysis.  OTOH, I do not quite follow why the main thread
(what is this ? initial thread ? what if it terminated already ?) should
receive the wakeup if it also blocks the signal.

Suggestion to check the thread sigmask before calling tdsigwakeup() is IMO =
the
right thing.

Spurious EINTR were allowed by POSIX, e.g. fork() in other thread might cau=
se
this (but not on FreeBSD).

--=20
You are receiving this mail because:
You are the assignee for the bug.=