On Wed, Jun 12, 2019 at 11:24:51AM -0400, Sinan Kaya wrote:
> On 6/12/2019 8:25 AM, Greg Kroah-Hartman wrote:
> > When calling debugfs functions, there is no need to ever check the
> > return value. The function can work or not, but the code logic should
> > never do something different based on this.
> >
> > Also, because there is no need to save the file dentry, remove the
> > variables that were saving them as they were never even being used once
> > set.
> >
> > Cc: Sinan Kaya <ok...@kernel.org>
> > Cc: Andy Gross <agr...@kernel.org>
> > Cc: David Brown <david.br...@linaro.org>
> > Cc: Dan Williams <dan.j.willi...@intel.com>
> > Cc: Vinod Koul <vk...@kernel.org>
> > Cc: linux-arm-ker...@lists.infradead.org
> > Cc: linux-arm-...@vger.kernel.org
> > Cc: dmaeng...@vger.kernel.org
> > Cc: linux-kernel@vger.kernel.org
> > Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>
>
> Interesting. Wouldn't debugfs_create_file() blow up if dir is NULL
> for some reason?
It will create a file in the root of debugfs. But how will that happen?
debugfs_create_dir() can not return NULL.
> + debugfs_create_file("stats", S_IRUGO, dir, chan,
> + &hidma_chan_fops);
>
> Note that code ignores the return value of hidma_debug_init();
> It was just trying to do clean up on debugfs failure by calling
>
> debugfs_remove_recursive(dmadev->debugfs);
Is that a problem?
thanks,
greg k-h
