From owner-freebsd-bugs@freebsd.org  Sun Jan 10 14:09:13 2016
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 C6464A6A1B0
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Sun, 10 Jan 2016 14:09:13 +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 B694A1935
 for <freebsd-bugs@FreeBSD.org>; Sun, 10 Jan 2016 14:09:13 +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 u0AE9DY1021036
 for <freebsd-bugs@FreeBSD.org>; Sun, 10 Jan 2016 14:09:13 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 202933] unwanted behaviour change when writing to revoked
 terminals
Date: Sun, 10 Jan 2016 14:09:14 +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-RELEASE
X-Bugzilla-Keywords: regression
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: fbsd.bugzilla@fenyo.net
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-202933-8-J6MW5Vufqb@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-202933-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-202933-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.20
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: Sun, 10 Jan 2016 14:09:13 -0000

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

--- Comment #3 from Alexandre Fenyo <fbsd.bugzilla@fenyo.net> ---
One more information about this problem:

This kernel change, that has modified the error number returned by a syscall
trying to write to a revoked console, that seems to me to be an ABI change =
in
the 10-Release major branch, breaks the rsyslogd port.

So, depending on the response to this bug ID (bug ID 202933) by FreeBSD ker=
nel
maintainers, I will have, or not, to report a patch proposal for rsyslogd:

- if this kernel change will stay with this new syscall return value, I'll
propose a patch in bug ID 202932 to let rsyslogd adapt itself to this new
return value of the kernel,

- and on the contrary, If kernel is to be patched, I will propose to close =
bug
ID 202932.

So, your answer is important for me to be able to work on BUG ID 202932.

Many thanks,

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