linux-kernel - Re: [RFC] net/mlx5: Fix failing fw tracer allocation on s390

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <7eaec712-6427-7adf-98cd-2c4347dd9e85@linux.ibm.com>
Date:   Wed, 8 Apr 2020 10:06:44 +0200
From:   Niklas Schnelle <schnelle@...ux.ibm.com>
To:     Markus Elfring <Markus.Elfring@....de>, netdev@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org,
        "David S. Miller" <davem@...emloft.net>,
        Eran Ben Elisha <eranbe@...lanox.com>,
        Leon Romanovsky <leon@...nel.org>,
        Moshe Shemesh <moshe@...lanox.com>,
        Saeed Mahameed <saeedm@...lanox.com>
Subject: Re: [RFC] net/mlx5: Fix failing fw tracer allocation on s390


On 4/7/20 5:12 PM, Markus Elfring wrote:
>> On s390 FORCE_MAX_ZONEORDER is 9 instead of 11, thus a larger kzalloc()
>> allocation as done for the firmware tracer will always fail.
> 
> How do you think about to add the tag “Fixes” to the final change description?
> 
> Regards,
> Markus
> 
You're right that makes a lot of sense, thanks! I guess this should reference
the commit that introduced the debug trace, right?

Best regards,
Niklas