netdev - Re: [PATCH net 0/7] mlxsw: Various fixes

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:   Wed, 10 Apr 2019 11:58:25 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     idosch@...lanox.com
Cc:     netdev@...r.kernel.org, jiri@...lanox.com, mlxsw@...lanox.com
Subject: Re: [PATCH net 0/7] mlxsw: Various fixes

From: Ido Schimmel <idosch@...lanox.com>
Date: Wed, 10 Apr 2019 06:58:10 +0000

> This patchset contains various small fixes for mlxsw.
> 
> Patch #1 fixes a warning generated by switchdev core when the driver
> fails to insert an MDB entry in the commit phase.
> 
> Patches #2-#4 fix a warning in check_flush_dependency() that can be
> triggered when a work item in a WQ_MEM_RECLAIM workqueue tries to flush
> a non-WQ_MEM_RECLAIM workqueue.
> 
> It seems that the semantics of the WQ_MEM_RECLAIM flag are not very
> clear [1] and that various patches have been sent to remove it from
> various workqueues throughout the kernel [2][3][4] in order to silence
> the warning.
> 
> These patches do the same for the workqueues created by mlxsw that
> probably should not have been created with this flag in the first place.
> 
> Patch #5 fixes a regression where an IP address cannot be assigned to a
> VRF upper due to erroneous MAC validation check. Patch #6 adds a test
> case.
> 
> Patch #7 adjusts Spectrum-2 shared buffer configuration to be compatible
> with Spectrum-1. The problem and fix are described in detail in the
> commit message.

Series applied.

> Please consider patches #1-#5 for 5.0.y. I verified they apply cleanly.

Queued up.