From owner-freebsd-bugs@freebsd.org  Tue Dec 19 16:43:47 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 76FDEE8F0DF
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Tue, 19 Dec 2017 16:43:47 +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 63D4B80B42
 for <freebsd-bugs@FreeBSD.org>; Tue, 19 Dec 2017 16:43:47 +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 vBJGhkX8063929
 for <freebsd-bugs@FreeBSD.org>; Tue, 19 Dec 2017 16:43:47 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 203366] kevent: EV_CLEAR on fifo does not work correctly
Date: Tue, 19 Dec 2017 16:43:46 +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.2-STABLE
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: jan.kokemueller@gmail.com
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: cc attachments.created
Message-ID: <bug-203366-8-f6hM4Wuglj@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-203366-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-203366-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.25
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: Tue, 19 Dec 2017 16:43:47 -0000

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

Jan Kokem=C3=BCller <jan.kokemueller@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jan.kokemueller@gmail.com

--- Comment #7 from Jan Kokem=C3=BCller <jan.kokemueller@gmail.com> ---
Created attachment 188967
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D188967&action=
=3Dedit
wake up pipe writers in edge triggered way

What do you think about the attached patch?

I believe the EV_EOF condition is cleared correctly by EV_CLEAR -- but each
time you try to read(2) at EOF the pipeselwakeup() down in pipe_read()
re-triggers the EOF condition. It should be enough to just wake up the writ=
ers
when there was actually some data read.

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