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: <20200324.172925.1546752299807440053.davem@davemloft.net>
Date:   Tue, 24 Mar 2020 17:29:25 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     saeedm@...lanox.com
Cc:     netdev@...r.kernel.org, kuba@...nel.org
Subject: Re: [pull request][net 0/5] Mellanox, mlx5 fixes 2020-03-24

From: Saeed Mahameed <saeedm@...lanox.com>
Date: Tue, 24 Mar 2020 14:52:52 -0700

> This series introduces some fixes to mlx5 driver.
> 
> From Aya, Fixes to the RX error recovery flows
> From Leon, Fix IB capability mask
> 
> Please pull and let me know if there is any problem.

Pulled.

> For -stable v5.5
>  ('net/mlx5_core: Set IB capability mask1 to fix ib_srpt connection failure')
> 
> For -stable v5.4
>  ('net/mlx5e: Fix ICOSQ recovery flow with Striding RQ')
>  ('net/mlx5e: Do not recover from a non-fatal syndrome')
>  ('net/mlx5e: Fix missing reset of SW metadata in Striding RQ reset')
>  ('net/mlx5e: Enhance ICOSQ WQE info fields')

Queued up.

> The above patch ('net/mlx5e: Enhance ICOSQ WQE info fields')
> will fail to apply cleanly on v5.4 due to a trivial contextual conflict, 
> but it is an important fix, do I need to do something about it or just
> assume Greg will know how to handle this ?

I'll do my best to backport it and ask for your help if necessary.

Thanks.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ