[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20171208.104613.2285331206958244059.davem@davemloft.net>
Date: Fri, 08 Dec 2017 10:46:13 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: bhole_prashant_q7@....ntt.co.jp
Cc: netdev@...r.kernel.org, jakub.kicinski@...ronome.com
Subject: Re: [PATCH net-next v2] netdevsim: remove return value check of
debugfs_create_dir
From: Prashant Bhole <bhole_prashant_q7@....ntt.co.jp>
Date: Fri, 8 Dec 2017 14:32:18 +0900
> Reason:
> Discussion started about adding error check on return value where
> it was not handled. Also handling the error using IS_ERR_OR_NULL
> instead of IS_ERR(), because debugfs_create_dir() doesn't return
> error. It returns NULL or a valid pointer when DebugFS is enabled.
>
> Finally it was decided to remove error handling altogether to
> make it consistent and removal of this check isn't fatal to the driver.
>
> Signed-off-by: Prashant Bhole <bhole_prashant_q7@....ntt.co.jp>
I'm not apply this.
If it fails with NULL at init time the will potentially place
all the netdevsim device files in the ROOT of debugfs which
is strongly undesriable.
Check the errors, fix the debugfs interface error return semantics,
and make errors fatal for module load.
Thank you.
Powered by blists - more mailing lists