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: <20190123211557.GA8556@ziepe.ca>
Date:   Wed, 23 Jan 2019 14:15:57 -0700
From:   Jason Gunthorpe <jgg@...pe.ca>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Doug Ledford <dledford@...hat.com>, linux-kernel@...r.kernel.org,
        linux-rdma@...r.kernel.org
Subject: Re: [PATCH 0/8] IB: cleanup debugfs usage

On Tue, Jan 22, 2019 at 04:17:52PM +0100, Greg Kroah-Hartman wrote:
> When calling debugfs code, there is no need to ever check the return
> value of the call, as no logic should ever change if a call works
> properly or not.  Fix up a bunch of infiniband-specific code to not care
> about the results of debugfs.
> 
> Greg Kroah-Hartman (8):
>   infiniband: cxgb4: no need to check return value of debugfs_create functions
>   infiniband: hfi1: drop crazy DEBUGFS_SEQ_FILE_CREATE() macro
>   infiniband: hfi1: no need to check return value of debugfs_create functions
>   infiniband: qib: no need to check return value of debugfs_create functions
>   infiniband: mlx5: no need to check return value of debugfs_create functions
>   infiniband: ocrdma: no need to check return value of debugfs_create functions
>   infiniband: usnic: no need to check return value of debugfs_create functions
>   infiniband: ipoib: no need to check return value of debugfs_create functions

Applied to rdma for-next

Thanks,
Jason

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ