Hi, All,
We checked the source codes of YAFFS and found that problem: The unlink of regular file is different from special file(including socket, device and directory). When unlinked, YAFFS delete special file from YAFFS object hash table, but the inode->i_count remains unchanged. We think that yaffs should not delete the special file when the inode->i_count is not 0, because deleting from hash table means freeing YAFFS object.
Currently we avoid this by mount any directories which will create special file and immediately unlink in tmpfs.
We think this bug(if this is a bug) is easy to fix. Anyone would do, or we do it?
Regards,
Russell Greece , Timmy Lee
----- Original Message -----
From: <guo@unication.com.cn>
To: <yaffs@toby-churchill.org>
Sent: Thursday, December 04, 2003 2:28 PM
Subject: maybe I found a bug?
> this email is a copy of my last one, the program is attached.
(text/plain)