Hi,

I've found an undiscovered bug in yaffs_unlink():
The problem arise when CONFIG_YAFFS_DISABLE_BACKGROUND_DELETION
is defined and we unlink() the last/only (hard)link to a file,
but this file is still opened by an application
(the attached program can show this quickly).

The problem is easy to understand:
	unlink(2) call	yaffs_unlink()
	who call	yaffs_Unlink()
	who call	yaffs_UnlinkWorker()
	who call	yaffs_UnlinkFile()
	who simply delete everything related to this file:
		directory entry, object header and data.

I will look for this tomorrow (European time).

I will appreciate if you CC any mail related to this to
my stupid email address at work: <project12@banksys.be>.

-- 
Luc Van Oostenryck