From owner-freebsd-hackers Sun Jun 6 20:14:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc1.sfba.home.com (ha1.rdc1.sfba.home.com [24.0.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 7B3AB14C40 for ; Sun, 6 Jun 1999 20:14:12 -0700 (PDT) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: from c62443-a.frmt1.sfba.home.com ([24.0.69.165]) by mail.rdc1.sfba.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19990607031412.HNZM8807.mail.rdc1.sfba.home.com@c62443-a.frmt1.sfba.home.com>; Sun, 6 Jun 1999 20:14:12 -0700 Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.8.7/8.8.7) id UAA10308; Sun, 6 Jun 1999 20:14:11 -0700 To: Brian Feldman Cc: hackers@FreeBSD.ORG Subject: Re: problem for the VM gurus References: From: Arun Sharma Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: 06 Jun 1999 20:14:11 -0700 In-Reply-To: Brian Feldman's message of "Sun, 6 Jun 1999 17:24:41 -0400 (EDT)" Message-ID: Lines: 32 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman writes: > In the long-standing tradition of deadlocks, I present to you all > a new one. This one locks in getblk, and causes other processes to > lock in inode. It's easy to induce, but I have no idea how I'd go > about fixing it myself (being very new to that part of the > kernel.) Here's the program which induces the deadlock: I could reproduce it with 4.0-current. The stack trace was: tsleep getblk bread ffs_read ffs_getpages vnode_pager_getpages vm_fault --- slow_copyin ffs_write vn_write dofilewrite write syscall getblk finds that the buffer is marked B_BUSY and sleeps on it. But I can't figure out who marked it busy. -Arun PS: Does anyone know how to get the stack trace by pid in ddb ? I can manually type trace p_addr>. But is there an easier way ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message