From owner-freebsd-current@freebsd.org Thu Feb 14 20:38:16 2019 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 6E28214E0CB6 for ; Thu, 14 Feb 2019 20:38:16 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3FF828AB8A; Thu, 14 Feb 2019 20:38:15 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id x1EKcDVj075910 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 14 Feb 2019 12:38:13 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id x1EKcDHv075909; Thu, 14 Feb 2019 12:38:13 -0800 (PST) (envelope-from sgk) Date: Thu, 14 Feb 2019 12:38:13 -0800 From: Steve Kargl To: John Baldwin Cc: freebsd-current@freebsd.org Subject: Re: Panic in sys_fstatat() Message-ID: <20190214203813.GA75902@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20190214024703.GA51003@troutmask.apl.washington.edu> <786f8034-b3ef-54cb-043b-e189e752b18b@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <786f8034-b3ef-54cb-043b-e189e752b18b@FreeBSD.org> User-Agent: Mutt/1.11.2 (2019-01-07) X-Rspamd-Queue-Id: 3FF828AB8A X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [2.13 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[sgk@troutmask.apl.washington.edu]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.07)[-0.074,0]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[washington.edu]; AUTH_NA(1.00)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; IP_SCORE(0.09)[ip: (0.17), ipnet: 128.95.0.0/16(0.24), asn: 73(0.10), country: US(-0.07)]; NEURAL_SPAM_SHORT(0.86)[0.864,0]; RCVD_IN_DNSWL_MED(-0.20)[21.76.95.128.list.dnswl.org : 127.0.11.2]; MX_GOOD(-0.01)[cached: troutmask.apl.washington.edu]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_SPAM_MEDIUM(0.56)[0.561,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:73, ipnet:128.95.0.0/16, country:US]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 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: Thu, 14 Feb 2019 20:38:16 -0000 On Thu, Feb 14, 2019 at 12:26:01PM -0800, John Baldwin wrote: > On 2/13/19 6:47 PM, Steve Kargl wrote: > > #16 0x00ff58bb in trap (frame=0x2e7b6880) at /usr/src/sys/i386/i386/trap.c:519 > > #17 0xffc0315d in ?? () > > #18 0x2e7b6880 in ?? () > > #19 0x00d1de64 in lookup (ndp=0x2e7b6a50) > > at /usr/src/sys/kern/vfs_lookup.c:710 > > #20 0x00d1d763 in namei (ndp=0x2e7b6a50) at /usr/src/sys/kern/vfs_lookup.c:487 > > #21 0x00d372c5 in kern_statat (td=0x3c5dc700, flag=0, fd=-100, > > path=0x2cced08e , > > pathseg=UIO_USERSPACE, sbp=0x2e7b6b18, hook=0x0) > > at /usr/src/sys/kern/vfs_syscalls.c:2307 > > #22 0x00d37c99 in sys_fstatat (td=0x3c5dc700, uap=0x3c5dc988) > > at /usr/src/sys/kern/vfs_syscalls.c:2284 > > #23 0x00ff69fa in syscallenter (td=) > > at /usr/src/sys/i386/i386/../../kern/subr_syscall.c:135 > > #24 syscall (frame=0x2e7b6ce8) at /usr/src/sys/i386/i386/trap.c:1144 > > #25 0xffc033a7 in ?? () > > #26 0x2e7b6ce8 in ?? () > > Backtrace stopped: Cannot access memory at address 0xfbafbbbc > > (kgdb) > > Frame 18 is probably the root problem, though it doesn't look like kgdb is > able to unwind it correctly. Looking at frame 19 might help though. It > seems like a NULL pointer dereference when invoking VOP_LOCK. > I can't look at this until tonight (about 6-7 hours). Anything in frame 19 that you would be particularly interested in? -- Steve