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

[Tejun Heo]

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/