netdev - Re: [PATCH mlx5-next] net/mlx5: Continue driver initialization despite debugfs failure

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: <d47a37f8e484e4356bdd3018db52e197003c1bad.camel@mellanox.com>
Date:   Mon, 17 Dec 2018 22:39:10 +0000
From:   Saeed Mahameed <saeedm@...lanox.com>
To:     "davem@...emloft.net" <davem@...emloft.net>,
        "leon@...nel.org" <leon@...nel.org>
CC:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        Leon Romanovsky <leonro@...lanox.com>,
        "linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>
Subject: Re: [PATCH mlx5-next] net/mlx5: Continue driver initialization
 despite debugfs failure

On Thu, 2018-12-13 at 13:15 +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@...lanox.com>
> 
> The failure to create debugfs entry is unpleasant event, but not
> enough
> to abort drier initialization. Align the mlx5_core code to debugfs
> design
> and continue execution whenever debugfs_create_dir() successes or
> not.
> 
> Fixes: e126ba97dba9 ("mlx5: Add driver for Mellanox Connect-IB
> adapters")
> Reviewed-by: Saeed Mahameed <saeedm@...lanox.com>
> Signed-off-by: Leon Romanovsky <leonro@...lanox.com>
> 

Applied to mlx5-next.

Thanks.