From owner-freebsd-bugs@FreeBSD.ORG Tue Sep 3 06:50:01 2013 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D123981A for ; Tue, 3 Sep 2013 06:50:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A295628D9 for ; Tue, 3 Sep 2013 06:50:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r836o1mZ068945 for ; Tue, 3 Sep 2013 06:50:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r836o1V5068943; Tue, 3 Sep 2013 06:50:01 GMT (envelope-from gnats) Date: Tue, 3 Sep 2013 06:50:01 GMT Message-Id: <201309030650.r836o1V5068943@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Yuri Subject: Re: kern/181741: [PATCH] Packet loss when ' control' messages are present with large data (sendmsg(2)) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Yuri List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Sep 2013 06:50:01 -0000 The following reply was made to PR kern/181741; it has been noted by GNATS. From: Yuri To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/181741: [PATCH] Packet loss when 'control' messages are present with large data (sendmsg(2)) Date: Mon, 02 Sep 2013 23:45:45 -0700 I originally came across this issue while running tmux (terminal multiplexer) under linuxlator. For some reason, tmux under linuxlator sends data into the local socket in larger portions on Linux, control message was included, and this exposed this bug. FreeBSD version of tmux doesn't expose this problem.