kern/48435: wierd file system behavior

[Jin Guojun [NCS]]

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

From: "Jin Guojun [NCS]" <j_guojun at lbl.gov>
To: Andy Farkas <andyf at speednet.com.au>
Cc: Kris Kennaway <kris at freebsd.org>,
	freebsd-gnats-submit at 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 at speednet.com.au
 >
 >         Andy Farkas
 >     System Administrator
 >    Speednet Communications
 >  http://www.speednet.com.au/