linux-kernel - Re: [PATCH v2] IB/mlx5: avoid excessive warning msgs when creating VFs on 2nd port

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]

Date:   Thu, 26 Jul 2018 16:12:14 -0600
From:   Jason Gunthorpe <jgg@...pe.ca>
To:     Qing Huang <qing.huang@...cle.com>
Cc:     linux-kernel@...r.kernel.org, linux-rdma@...r.kernel.org,
        dledford@...hat.com, leon@...nel.org, gerald.gibson@...cle.com,
        danielj@...lanox.com, sharon.s.liu@...cle.com
Subject: Re: [PATCH v2] IB/mlx5: avoid excessive warning msgs when creating
 VFs on 2nd port

On Mon, Jul 23, 2018 at 02:15:08PM -0700, Qing Huang wrote:
> When a CX5 device is configured in dual-port RoCE mode, after creating
> many VFs against port 1, creating the same number of VFs against port 2
> will flood kernel/syslog with something like
> "mlx5_*:mlx5_ib_bind_slave_port:4266:(pid 5269): port 2 already
> affiliated."
> 
> So basically, when traversing mlx5_ib_dev_list, mlx5_ib_add_slave_port()
> repeatedly attempts to bind the new mpi structure to every device
> on the list until it finds an unbound device.
> 
> Change the log level from warn to dbg to avoid log flooding as the warning
> should be harmless.
> 
> Signed-off-by: Qing Huang <qing.huang@...cle.com>
> Reviewed-by: Daniel Jurgens <danielj@...lanox.com>
> ---
>   v1 -> v2: change the log level instead

Applied to for-next

Thanks,
Jason