From owner-freebsd-current@freebsd.org Mon Oct 1 09:19:24 2018 Return-Path: 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 E2E0610A8CB1 for ; Mon, 1 Oct 2018 09:19:23 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 800AB96225 for ; Mon, 1 Oct 2018 09:19:23 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mail-qt1-x829.google.com with SMTP id n6-v6so13170695qtl.4 for ; Mon, 01 Oct 2018 02:19:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Zde57k5kUp+RWSF/SF+c987e6X+Cdn1QD+H5y2Xpzrs=; b=SEfXu3Q1wwr5fnexvXdrLdeh51INlXXZEW+m56Mbm2bzJeWvqW4GyQn/fDpA7Xo1qF yVXY1c6Z3lYAj+PWZ7+FyazoHwXHlCt/TYOtZTlgZqAVYycwIjhLIfIe8NTdJbi4ZKB2 PVYQrFrF1ki6tu0qAkEEdJ+S0BmJ1HbYhHkM32KR3bzjNEK5yDTehuShfmWvR7lQYblA Pv+1NRr48EKjyejgeLLAU+wGNKjnt0ERqWaX4hRvbfJdLzpfl5RWyD/2XmSd7J9fpN3m iN7TJEFcsvdpWkFBiP36SFrVbzAxoVTqxzKJq12MEUKBWMNC8Jz7xOolIJGfO70i8MnG l82Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Zde57k5kUp+RWSF/SF+c987e6X+Cdn1QD+H5y2Xpzrs=; b=ctsh6YLi2q4MC5HItEJypf87sRIKRmKZT87fUAdoiUsBrvF42aBkOkhd1bi4dO4OlJ MaDViFhN8uORPn6uPwd/ElwxxhLxWd0ZSJjkeoTvY8df0SPj0w/zAU5pNJCfQvCC0wqs 9WHxIAUkB/X5VOS5IlLHBg/VCNDxaemadKjHoH8GuQA1Bw0yiyK1U4LjSzPbtiBxpUND rFk30DhT6VEFnnwcxyIt0IU6h48pLjjo2NW415v/ANwENhtN3R1qHDAu0maSsN80us6W owr8+9fKg0B64Do0K7Dkaf3/A2hwEPv5F1PhjssejwPeLLsaY7kcGXKaGnt61rSMOtLN pnhA== X-Gm-Message-State: ABuFfoj1Wjl1cn+TNBUqkPeQNo9W+XirsNlnZXzIWaO5vHb/PTFgBXWV xX0LETgv9pMXhQ/3u3NP/a9I9OndDV1zqlRGwSY= X-Google-Smtp-Source: ACcGV6276AmjB53rLui2Fz/dJgrzU5hFV4St4KfZUtN+/Gejy8Gk5Gl+JztONPA73JSSBfYuVXnrOK2zYcJgicPyq/Y= X-Received: by 2002:a05:6214:110d:: with SMTP id e13mr7387272qvs.182.1538385563120; Mon, 01 Oct 2018 02:19:23 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac8:362e:0:0:0:0:0 with HTTP; Mon, 1 Oct 2018 02:19:22 -0700 (PDT) In-Reply-To: <20181001090031.GC5335@kib.kiev.ua> References: <20181001090031.GC5335@kib.kiev.ua> From: Mateusz Guzik Date: Mon, 1 Oct 2018 11:19:22 +0200 Message-ID: Subject: Re: vmstat -m and netstat -m dumping core when run on vmcores To: Konstantin Belousov Cc: Yuri Pankov , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Mailman-Approved-At: Mon, 01 Oct 2018 15:05:55 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Oct 2018 09:19:24 -0000 On 10/1/18, Konstantin Belousov wrote: > 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=, >> argv=0x00007fffffffeb28) at vmstat.c:386 >> frame #3: 0x0000000000204095 vmstat`_start(ap=, >> cleanup=) 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. > Indeed, I'll take care of it. Thanks for the report. -- Mateusz Guzik