From owner-freebsd-hackers@freebsd.org  Mon Oct 22 13:30:07 2018
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7D73EFFBE5E
 for <freebsd-hackers@mailman.ysv.freebsd.org>;
 Mon, 22 Oct 2018 13:30:07 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
 (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 174F079D44;
 Mon, 22 Oct 2018 13:30:07 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1gEaHL-00054P-Ri; Mon, 22 Oct 2018 16:29:55 +0300
Date: Mon, 22 Oct 2018 16:29:55 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Lev Serebryakov <lev@FreeBSD.org>
Cc: Alan Somers <asomers@freebsd.org>,
 "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>,
 cse.cem@gmail.com
Subject: Re: What is wrong with dtrace's stack()?
Message-ID: <20181022132955.GB1809@zxy.spb.ru>
References: <170994671.20181021201021@serebryakov.spb.ru>
 <CAG6CVpVCe-8OVU+KEyAh8swFSAjRshNcNLN0tjAS3W8bZxyrTA@mail.gmail.com>
 <475670271.20181022003734@serebryakov.spb.ru>
 <CAOtMX2goztCYJXM72WNR711DEBEKAGk1zFHF=NpE4UiVAF2bAQ@mail.gmail.com>
 <234d745d-37a9-9610-15b9-0f5cd5af21bf@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <234d745d-37a9-9610-15b9-0f5cd5af21bf@FreeBSD.org>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2018 13:30:07 -0000

On Mon, Oct 22, 2018 at 02:45:19PM +0300, Lev Serebryakov wrote:

> sosend() calls protocol-specific handler via function pointer, so it
> should be true call:
> 
> CURVNET_SET(so->so_vnet);
> if (!SOLISTENING(so))
> 	error = so->so_proto->pr_usrreqs->pru_sosend(so, addr, uio,
> 	    top, control, flags, td);
> else {
> 	m_freem(top);
> 	m_freem(control);
> 	error = ENOTCONN;
> }
> CURVNET_RESTORE();
> return (error);
> 
>   These frames MUST be here...

(kgdb) x/80i sosend
0xffffffff8054d6b0 <sosend>:    push   %rbp
0xffffffff8054d6b1 <sosend+1>:  mov    %rsp,%rbp
0xffffffff8054d6b4 <sosend+4>:  mov    0x20(%rdi),%rax
0xffffffff8054d6b8 <sosend+8>:  mov    0x58(%rax),%rax
0xffffffff8054d6bc <sosend+12>: mov    0x98(%rax),%rax
0xffffffff8054d6c3 <sosend+19>: pop    %rbp
0xffffffff8054d6c4 <sosend+20>: jmpq   *%rax