From mboxrd@z Thu Jan 1 00:00:00 1970 From: Raghavendra K T Subject: Re: [PATCH 3.12-rc7] KVM: Fix modprobe failure for kvm_intel/kvm_amd Date: Wed, 30 Oct 2013 19:25:20 +0530 Message-ID: <52710FC8.8060309@linux.vnet.ibm.com> References: <1383059634-55512-1-git-send-email-tim.gardner@canonical.com> <52700C24.9050001@linux.vnet.ibm.com> <20131029200012.GA19769@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Linus Torvalds , Tim Gardner , Linux Kernel Mailing List , the arch/x86 maintainers , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Gleb Natapov , Marcelo Tosatti , Paolo Bonzini , KVM list , Al Viro To: Greg KH Return-path: In-Reply-To: <20131029200012.GA19769@kroah.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org 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.