From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: Re: [PATCH v2 net] mlx4_core: restore optimal ICM memory allocation Date: Fri, 1 Jun 2018 05:57:42 -0400 Message-ID: <42473b16-e9c0-f556-4538-e4c47b2b1f1e@gmail.com> References: <20180531125224.97098-1-edumazet@google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: netdev , Eric Dumazet , John Sperbeck , Tarick Bedeir , Daniel Jurgens , Zhu Yanjun To: Qing Huang , Eric Dumazet , "David S . Miller" Return-path: Received: from mail-pg0-f68.google.com ([74.125.83.68]:37505 "EHLO mail-pg0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750790AbeFAJ5p (ORCPT ); Fri, 1 Jun 2018 05:57:45 -0400 Received: by mail-pg0-f68.google.com with SMTP id a13-v6so11047941pgu.4 for ; Fri, 01 Jun 2018 02:57:44 -0700 (PDT) In-Reply-To: Content-Language: en-US Sender: netdev-owner@vger.kernel.org List-ID: 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.