Messages in this thread | | | Date | Wed, 30 Oct 2013 19:25:20 +0530 | From | Raghavendra K T <> | Subject | Re: [PATCH 3.12-rc7] KVM: Fix modprobe failure for kvm_intel/kvm_amd |
| |
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.
| |