Re: [Bluez-devel] Oops involving RFCOMM and sysfs

Tejun Heo
2008-01-07T09:17:37Z

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. :-)

--
tejun