From owner-freebsd-current@freebsd.org  Mon Oct  1 09:00:43 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@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 3972810A6B94
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Mon,  1 Oct 2018 09:00:43 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1])
 (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 9413E957A6;
 Mon,  1 Oct 2018 09:00:42 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from tom.home (kib@localhost [127.0.0.1])
 by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w9190Vlt079972
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Mon, 1 Oct 2018 12:00:34 +0300 (EEST)
 (envelope-from kostikbel@gmail.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w9190Vlt079972
Received: (from kostik@localhost)
 by tom.home (8.15.2/8.15.2/Submit) id w9190VV6079967;
 Mon, 1 Oct 2018 12:00:31 +0300 (EEST)
 (envelope-from kostikbel@gmail.com)
X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com
 using -f
Date: Mon, 1 Oct 2018 12:00:31 +0300
From: Konstantin Belousov <kostikbel@gmail.com>
To: Yuri Pankov <yuripv@yuripv.net>
Cc: freebsd-current <freebsd-current@freebsd.org>, mjg@freebsd.org
Subject: Re: vmstat -m and netstat -m dumping core when run on vmcores
Message-ID: <20181001090031.GC5335@kib.kiev.ua>
References: <a340dd41-9ab9-5330-39c8-d188616e0244@yuripv.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <a340dd41-9ab9-5330-39c8-d188616e0244@yuripv.net>
User-Agent: Mutt/1.10.1 (2018-07-13)
X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00,
 DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM,
 NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tom.home
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Oct 2018 09:00:43 -0000

On Mon, Oct 01, 2018 at 09:15:46AM +0300, Yuri Pankov wrote:
> Hi,
> 
> I've noticed the following rebooting after a panic:
> 
> pid 41246 (vmstat), uid 0: exited on signal 11 (core dumped)
> pid 47091 (netstat), uid 0: exited on signal 11
> 
> And indeed, trying to manually run those on the resulting vmcore makes 
> them crash:
> 
> # vmstat -m -M /var/crash/vmcore.0
> Segmentation fault (core dumped)
> # netstat -m -M /var/crash/vmcore.0
> Segmentation fault
> 
> Backtrace is below:
> 
> * thread #1, name = 'vmstat', stop reason = signal SIGSEGV
>    * frame #0: 0x000000080026d19f 
> libmemstat.so.3`memstat_kvm_malloc(list=0x00000008007c5000, 
> kvm_handle=0x000000080070e000) at memstat_malloc.c:351
>      frame #1: 0x0000000000204b15 vmstat`main [inlined] domemstat_malloc 
> at vmstat.c:1406
>      frame #2: 0x0000000000204af4 vmstat`main(argc=<unavailable>, 
> argv=0x00007fffffffeb28) at vmstat.c:386
>      frame #3: 0x0000000000204095 vmstat`_start(ap=<unavailable>, 
> cleanup=<unavailable>) at crt1.c:74
> 
> Wonder if it's just me or something is broken here?

I think this is due to r338899.  libmemstat needs an adjustments to handle
that.