From owner-freebsd-bugs@FreeBSD.ORG  Mon Jul 14 16:00:35 2003
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5A2BC37B401
	for <freebsd-bugs@hub.freebsd.org>;
	Mon, 14 Jul 2003 16:00:35 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id F24D843FB1
	for <freebsd-bugs@hub.freebsd.org>;
	Mon, 14 Jul 2003 16:00:34 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h6EN0YUp015620
	for <freebsd-bugs@freefall.freebsd.org>;
	Mon, 14 Jul 2003 16:00:34 -0700 (PDT)
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h6EN0YLF015619;
	Mon, 14 Jul 2003 16:00:34 -0700 (PDT)
Date: Mon, 14 Jul 2003 16:00:34 -0700 (PDT)
Message-Id: <200307142300.h6EN0YLF015619@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
From: "Jin Guojun [NCS]" <j_guojun@lbl.gov>
Subject: Re: kern/48435: wierd file system behavior
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: "Jin Guojun \[NCS\]" <j_guojun@lbl.gov>
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jul 2003 23:00:35 -0000

The following reply was made to PR kern/48435; it has been noted by GNATS.

From: "Jin Guojun [NCS]" <j_guojun@lbl.gov>
To: Andy Farkas <andyf@speednet.com.au>
Cc: Kris Kennaway <kris@freebsd.org>,
	freebsd-gnats-submit@freebsd.org
Subject: Re: kern/48435: wierd file system behavior
Date: Mon, 14 Jul 2003 16:04:33 -0700

 This was not a feature until 4.7-RELEASE.
 Also, I do not believe that other file system/UN*X does this.
 If this is not file system issue, but tar, then tar needs to be fixed.
 
 A couple of problems this behavior creates:
 (1) If a process is staying and running in this directory, it will be killed
 when directory (inode) is disappearing.
 (2) Fire off security alarm when a directory inode changed.
 
     -Jin
 
 Andy Farkas wrote:
 
 > I don't think this is a bug. Its what tar does.
 >
 > A truss of tar when the directory exists, but has no files:
 >
 > mkdir(0x809b070,0x1ed)          ERR#17 'File exists'
 > unlink(0x809b070)               ERR#1 'Operation not permitted'
 > rmdir(0x809b070)                = 0 (0x0)
 > mkdir(0x809b070,0x1ed)          = 0 (0x0)
 >
 > But when a file exists in the directory:
 >
 > mkdir(0x809b070,0x1ed)          ERR#17 'File exists'
 > unlink(0x809b070)               ERR#1 'Operation not permitted'
 > rmdir(0x809b070)                ERR#66 'Directory not empty'
 >
 > So it seems tar is removing then creating the directory if it is empty.
 >
 > --
 >
 >  :{ andyf@speednet.com.au
 >
 >         Andy Farkas
 >     System Administrator
 >    Speednet Communications
 >  http://www.speednet.com.au/