From owner-freebsd-bugs Mon Jun 19 17: 0: 8 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 7DF1337B824 for ; Mon, 19 Jun 2000 17:00:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id RAA70149; Mon, 19 Jun 2000 17:00:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Mon, 19 Jun 2000 17:00:03 -0700 (PDT) Message-Id: <200006200000.RAA70149@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Richard A. Steenbergen" Subject: Re: kern/19389: sendfile(2) Reply-To: "Richard A. Steenbergen" 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: "Richard A. Steenbergen" To: David Greenman Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/19389: sendfile(2) Date: Mon, 19 Jun 2000 19:59:30 -0400 (EDT) On Mon, 19 Jun 2000, David Greenman wrote: > > 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? I wish I had let the coredump go. Kernel panic from ncftpd sendfile, immediately after I rm -rf'd the files in another console. -- Richard A Steenbergen http://www.e-gerbil.net/humble PGP Key ID: 0x138EA177 (67 29 D7 BC E8 18 3E DA B2 46 B3 D8 14 36 FE B6) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message