From owner-freebsd-bugs@freebsd.org Thu Aug 31 08:15:00 2017 Return-Path: Delivered-To: freebsd-bugs@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 654BFE18BF0 for ; Thu, 31 Aug 2017 08:15:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 5371E6E092 for ; Thu, 31 Aug 2017 08:15:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v7V8Ex15081183 for ; Thu, 31 Aug 2017 08:15:00 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 191359] [memguard] [panic] Memory modified after free w/MEMGUARD build Date: Thu, 31 Aug 2017 08:14:59 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: pho@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Aug 2017 08:15:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D191359 --- Comment #9 from Peter Holm --- (In reply to Siva Mahadevan from comment #8) Hard for me to say it the original panic is still there. With the same scenario I see: panic: MemGuard detected double-free of 0xfffffe000075e000 cpuid =3D 2 time =3D 1504166229 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe2ebbde5= db0 vpanic() at vpanic+0x19c/frame 0xfffffe2ebbde5e30 panic() at panic+0x43/frame 0xfffffe2ebbde5e90 memguard_free() at memguard_free+0x14f/frame 0xfffffe2ebbde5ed0 bufkva_free() at bufkva_free+0xf8/frame 0xfffffe2ebbde5ef0 buf_free() at buf_free+0xd5/frame 0xfffffe2ebbde5f40 brelse() at brelse+0x5c0/frame 0xfffffe2ebbde5fd0 bufdone_finish() at bufdone_finish+0xd4/frame 0xfffffe2ebbde5ff0 bufdone() at bufdone+0xe3/frame 0xfffffe2ebbde6020 biodone() at biodone+0x188/frame 0xfffffe2ebbde6060 g_io_deliver() at g_io_deliver+0x5e4/frame 0xfffffe2ebbde6140 biodone() at biodone+0x188/frame 0xfffffe2ebbde6180 g_io_deliver() at g_io_deliver+0x5e4/frame 0xfffffe2ebbde6260 biodone() at biodone+0x188/frame 0xfffffe2ebbde62a0 g_io_deliver() at g_io_deliver+0x5e4/frame 0xfffffe2ebbde6380 g_disk_done() at g_disk_done+0x1ee/frame 0xfffffe2ebbde6400 biodone() at biodone+0x188/frame 0xfffffe2ebbde6440 dadone() at dadone+0x194b/frame 0xfffffe2ebbde69a0 xpt_done_process() at xpt_done_process+0x35f/frame 0xfffffe2ebbde69e0 xpt_done_td() at xpt_done_td+0x136/frame 0xfffffe2ebbde6a30 fork_exit() at fork_exit+0x13b/frame 0xfffffe2ebbde6ab0 Details @ https://people.freebsd.org/~pho/stress/log/memguard8.txt --=20 You are receiving this mail because: You are the assignee for the bug.=