From owner-freebsd-bugs Mon Jun 19 17: 0: 6 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 417DA37B806 for ; Mon, 19 Jun 2000 17:00:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id RAA70144; Mon, 19 Jun 2000 17:00:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Mon, 19 Jun 2000 17:00:02 -0700 (PDT) Message-Id: <200006200000.RAA70144@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: David Greenman Subject: Re: kern/19389: sendfile(2) Reply-To: David Greenman Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/19389; it has been noted by GNATS. From: David Greenman To: ras@e-gerbil.net Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/19389: sendfile(2) Date: Mon, 19 Jun 2000 16:48:20 -0700 > Deleting a file while doing a sendfile(2) on it results in > kernel panic. Non-priv'd users can panic box. This is a case that I've specifically tested for in the past, so I'm a bit surprised to see this bug report. sendfile(2) holds a vnode reference to the file (via the open file descriptor), which should prevent bad things from happening when the file is unlinked (the actual deletion is defered until all internal references have been dropped). Is it possible that there is more involved than just deleting the file? Can you provide a traceback? -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org Manufacturer of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message