From owner-freebsd-amd64@freebsd.org  Mon Jan 16 17:37:37 2017
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@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 08C86CB1C10
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Mon, 16 Jan 2017 17:37:37 +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 ECBAD1EA9
 for <freebsd-amd64@FreeBSD.org>; Mon, 16 Jan 2017 17:37:36 +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 v0GHbawn023075
 for <freebsd-amd64@FreeBSD.org>; Mon, 16 Jan 2017 17:37:36 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 216089] bsnmp sendmsg: Invalid argument
Date: Mon, 16 Jan 2017 17:37:36 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 11.0-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: ngie@FreeBSD.org
X-Bugzilla-Status: Closed
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: resolution cc bug_status
Message-ID: <bug-216089-6-A18eSPaJYt@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-216089-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-216089-6@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-amd64@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Jan 2017 17:37:37 -0000

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

Ngie Cooper <ngie@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
                 CC|                            |ngie@FreeBSD.org
             Status|New                         |Closed

--- Comment #1 from Ngie Cooper <ngie@FreeBSD.org> ---
I apologize for the breakage. This issue should be resolved by the following
MFCs to ^/stable/11 and ^/stable/10:

- https://svnweb.freebsd.org/base?view=3Drevision&revision=3D312264
- https://svnweb.freebsd.org/base?view=3Drevision&revision=3D312265

(they were going to be MFCed later on this week, but after I realized the
breakage that I introduced by accident, I MFCed "ahead of schedule").

Please let me know how your testing goes.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=