netdev - Re: [PATCH] l2tp: no need to check return value of debugfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20190614.084523.409954717487562128.davem@davemloft.net>
Date:   Fri, 14 Jun 2019 08:45:23 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     gregkh@...uxfoundation.org
Cc:     g.nault@...halink.fr, netdev@...r.kernel.org
Subject: Re: [PATCH] l2tp: no need to check return value of debugfs_create
 functions

From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Date: Fri, 14 Jun 2019 09:04:38 +0200

> 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, there is no need to store the individual debugfs file name, just
> remove the whole directory all at once, saving a local variable.
> 
> Cc: "David S. Miller" <davem@...emloft.net>
> Cc: Guillaume Nault <g.nault@...halink.fr>
> Cc: netdev@...r.kernel.org
> Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>

Applied.