Messages in this thread |  | | | Date | Mon, 07 Jan 2008 18:18:21 +0900 | | From | Tejun Heo <> | | Subject | Re: [Bluez-devel] Oops involving RFCOMM and sysfs | |
Tejun Heo wrote:
> Eric W. Biederman wrote:
>>> That said, the mechanism is a bit too fragile. sysfs currently ensures
>>> that dentry/inode point to the associated sysfs_dirent. This is mainly
>>> remanent of conversion from previous VFS based implementation. I think
>>> the right thing to do here is to make sysfs behave like other proper
>>> distributed filesystems using d_revalidate.
>> Huh? We still need something like sysfs_get_dentry to find the dentries
>> for the rename or move operation. So we can call d_move.
>
> Ah... right. Thanks. :-)
On the second thought, can't those too be dealt with d_revalidate?
--
tejun
|  |