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.