From owner-freebsd-net@freebsd.org  Tue Aug  8 11:56:38 2017
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@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 C5783DD70D5;
 Tue,  8 Aug 2017 11:56:38 +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 6B42D83135;
 Tue,  8 Aug 2017 11:56:38 +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 1df37j-000K9C-Cs; Tue, 08 Aug 2017 14:56:35 +0300
Date: Tue, 8 Aug 2017 14:56:35 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Hans Petter Selasky <hps@selasky.org>
Cc: FreeBSD Net <freebsd-net@freebsd.org>,
 FreeBSD Stable <freebsd-stable@freebsd.org>,
 Ben RUBSON <ben.rubson@gmail.com>,
 hiren <hiren@strugglingcoder.info>, jch <jch@FreeBSD.org>
Subject: Re: mlx4en, timer irq @100%... (11.0 stuck on high network load ???)
Message-ID: <20170808115635.GY1585@zxy.spb.ru>
References: <2ADA8C57-2C2D-4F97-9F0B-82D53EDDC649@gmail.com>
 <061cdf72-6285-8239-5380-58d9d19a1ef7@selasky.org>
 <92BEE83D-498F-47D5-A53C-39DCDC00A0FD@gmail.com>
 <5d8960d8-e1ff-8719-320f-d3ae84054714@selasky.org>
 <6B4A35F7-5694-4945-9575-19ADB678F9FA@gmail.com>
 <297a784a-3d80-b1a6-652e-a78621fe5a8b@selasky.org>
 <3ECCFBF1-18D9-4E33-8F39-0C366C3BB8B4@gmail.com>
 <c05c2b1c-b5a8-c39c-6dff-e6cc0d8642bf@selasky.org>
 <20170808113352.GH18123@zxy.spb.ru>
 <f006e193-29b6-689a-8957-04d412969ace@selasky.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <f006e193-29b6-689a-8957-04d412969ace@selasky.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-net@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Aug 2017 11:56:38 -0000

On Tue, Aug 08, 2017 at 01:49:08PM +0200, Hans Petter Selasky wrote:

> On 08/08/17 13:33, Slawa Olhovchenkov wrote:
> > TW_RUNLOCK(V_tw_lock);
> > and
> > if (INP_INFO_TRY_WLOCK(&V_tcbinfo)) {
> > 
> > `inp` can be invalidated, freed and this pointer may be invalid?
> 
> If you look one line up there is a pcbref ??

Yes.
Can different thread take this inp and freed it?
May be timer thread?