Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757926AbcK3ObS (ORCPT ); Wed, 30 Nov 2016 09:31:18 -0500 Received: from mail-wm0-f65.google.com ([74.125.82.65]:34236 "EHLO mail-wm0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757227AbcK3ObI (ORCPT ); Wed, 30 Nov 2016 09:31:08 -0500 MIME-Version: 1.0 In-Reply-To: <583E8864.9000305@huawei.com> References: <583E8864.9000305@huawei.com> From: Andrey Ryabinin Date: Wed, 30 Nov 2016 17:31:06 +0300 Message-ID: Subject: Re: [RFC] kasan: is it a wrong report from kasan? To: Xishi Qiu Cc: yang.shi@linaro.org, Steven Rostedt , Linux MM , LKML , Yisheng Xie , wangwei Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 378 Lines: 9 2016-11-30 11:05 GMT+03:00 Xishi Qiu : > The kernel version is v4.1, and I find some error reports from kasan. > I'm not sure whether it is a wrong report. > This looks like false positive that was fixed in 0d97e6d8024("arm64: kasan: clear stale stack poison"). Also you might need e1b77c92981a("sched/kasan: remove stale KASAN poison after hotplug") too.