On 10/30/2013 01:30 AM, Greg KH wrote:
[...]
debugfs_create_dir() currently returns NULL dentry on both
EEXIST, ENOMEM ... cases.
Could one solution be cascading actual error
that is lost in fs/debugfs/inode.c:__create_file(), so that we could
take correct action in case of failure of debugfs_create_dir()?
What would you do here? You shouldn't really care about debugfs files,
if there's an error, keep on going, no code path should really care,
right?
Thanks Greg.
Yes you are right. we can't do anything useful after that error.
If debugfs directories are not critical, may be we could
continue from there.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
