netdev - Re: [PATCH v2 net] mlx4_core: restore optimal ICM memory allocation

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: <42473b16-e9c0-f556-4538-e4c47b2b1f1e@gmail.com>
Date:   Fri, 1 Jun 2018 05:57:42 -0400
From:   Eric Dumazet <eric.dumazet@...il.com>
To:     Qing Huang <qing.huang@...cle.com>,
        Eric Dumazet <edumazet@...gle.com>,
        "David S . Miller" <davem@...emloft.net>
Cc:     netdev <netdev@...r.kernel.org>,
        Eric Dumazet <eric.dumazet@...il.com>,
        John Sperbeck <jsperbeck@...gle.com>,
        Tarick Bedeir <tarick@...gle.com>,
        Daniel Jurgens <danielj@...lanox.com>,
        Zhu Yanjun <yanjun.zhu@...cle.com>
Subject: Re: [PATCH v2 net] mlx4_core: restore optimal ICM memory allocation



On 05/31/2018 09:51 PM, Qing Huang wrote:
> 

> It would be great if you could share the test case that triggered the KASAN report in your
> environment. Our QA has been running intensive tests using 8KB or 4KB chunk size configuration
> for some time, no one has reported memory corruption issues so far, given that we are not
> running the latest upstream kernel.
> 
> IMO, it's worthwhile to find out the root cause and fix the problem.
> 

Do not worry, we are working on this minor problem.

We do not use KASAN on production hosts, quite obviously.

The memory waste is the major problem really.