Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp65390pxu; Tue, 1 Dec 2020 06:17:06 -0800 (PST) X-Google-Smtp-Source: ABdhPJw/v8Z0QSpDaLnZgHoKgAVj61oOFfnRuFOBcGQoEx9YHvFvQE78REkd0+M9sGbK/xFV5zSS X-Received: by 2002:a17:906:1e84:: with SMTP id e4mr3151315ejj.57.1606832225839; Tue, 01 Dec 2020 06:17:05 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1606832225; cv=none; d=google.com; s=arc-20160816; b=WRt5R/bAWECuaQXlvfRwf/X51S4LOs9a336CqAN95uNqjW01ldfuww/fR0qDCuZ2q1 N0y509GzNXFxCb0HKbiTrB3o5o/+Q0/Maipwj1N1PxINL1cwdfchkeFlG+FDD8VEUAJb oZgHLEWMikqGyOdd8n2MWgKe/lMC67LSm9MHDZ6zkHvRn6Vh1pqOS9/iScO0hZGId2kH xLkEM9r/XJQFDShGr18HW7H/HCGe6ZvJ0ew8dycWyKmiUGWt6VvlFi/XpjAvcrLAUkOE eHkUlixCDYSibuH4WfLxVW3r9hAtZtE7GXysghirpAxIsiAPJ+4sBDjRf8U9wo9bpvji Zq0g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:dkim-signature:dkim-signature:from; bh=Skhg6O9p2Trnjrbm81ayS393ZogAa9PiayeejAPB7Ow=; b=veU81PwMWhblfTSc0ZtaN9Jo7Bbnl5rCnwVCVJZa+Ais4kK2S1vEzDMffgvdYA4Ia4 HDJX0+M0msiCbHLuapZx//Jxw7/LPDltDOWqgrloxl0cVcfqgjRBDs/vAlPz72ZvelRg m714APdxlcc4hSP4NEIfgobO/UcujZTKYbS0G+CjEfM8EIeLoBWeSGv6E1rNFpVxf0dn 7iHfE2vqLRDzgbUSfHPyo/qTYjRP7PKjJfxVePn6JMD3lUHFHVBJM+VkQMwJewRcx6g4 kSNHph/fT2rg6an/ISszxxJHTsgWumqEttIAC+8PHEX1+rwke+0RbK8x4vxGyTWOnpIy 1jmA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=Mw9HOaWV; dkim=neutral (no key) header.i=@linutronix.de header.b=+uah8n9H; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d13si1215454edv.602.2020.12.01.06.16.40; Tue, 01 Dec 2020 06:17:05 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=Mw9HOaWV; dkim=neutral (no key) header.i=@linutronix.de header.b=+uah8n9H; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730590AbgLAOOU (ORCPT + 99 others); Tue, 1 Dec 2020 09:14:20 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43650 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730334AbgLAOOT (ORCPT ); Tue, 1 Dec 2020 09:14:19 -0500 Received: from galois.linutronix.de (Galois.linutronix.de [IPv6:2a0a:51c0:0:12e:550::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D680DC0613D6 for ; Tue, 1 Dec 2020 06:13:38 -0800 (PST) From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1606832016; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Skhg6O9p2Trnjrbm81ayS393ZogAa9PiayeejAPB7Ow=; b=Mw9HOaWVR79l72uLb07taz0LhZWUg8d2/HcmPfRcpZ4cCq6AZpzlRRr0IS9gzoIga3r+bO NywKzYVIGI/2M4ARyuCPl0/wuC1Xp5OFqTHMuYEFR/xerUVW4pEyqOwq9RPANMLUr8nnj6 nK9RgMhl6/iHcXlj1MwZtbBiTQlJji+h1+OSgVyxaylqkdMQxxNPKZEBzgS1T4VuBACrXQ 7H1zXyEIEeWWp673BEURkomaOIfS0UWl5PrTTAX9WUAp02CCJRLpzcXYMylMEtig3BnurG 3WDPJBaoWh8ly+UtGwljZirT85nz/Lqkgx/ANbTHgmcfETrHkj5MPa/PVfoMgw== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1606832016; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Skhg6O9p2Trnjrbm81ayS393ZogAa9PiayeejAPB7Ow=; b=+uah8n9H51Y4ejsCR0Zmx8WPPwKY1FEz2dTA8w9rlY73cNkQ3nWGd3qzkRRjnXqZVhA9ir 2eJhR8yltoybsLAg== To: Dmitry Vyukov Cc: Walter Wu , Andrew Morton , John Stultz , Stephen Boyd , Tejun Heo , Lai Jiangshan , Marco Elver , Andrey Ryabinin , Alexander Potapenko , Andrey Konovalov , Matthias Brugger , kasan-dev , Linux-MM , LKML , Linux ARM , wsd_upstream , linux-mediatek@lists.infradead.org Subject: Re: [PATCH v4 0/6] kasan: add workqueue and timer stack for generic KASAN In-Reply-To: References: <20200924040152.30851-1-walter-zh.wu@mediatek.com> <87h7rfi8pn.fsf@nanos.tec.linutronix.de> Date: Tue, 01 Dec 2020 15:13:36 +0100 Message-ID: <871rg9hawf.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Dec 01 2020 at 08:59, Dmitry Vyukov wrote: > On Wed, Sep 30, 2020 at 5:29 PM Thomas Gleixner wrote: >> On Thu, Sep 24 2020 at 12:01, Walter Wu wrote: >> > Syzbot reports many UAF issues for workqueue or timer, see [1] and [2]. >> > In some of these access/allocation happened in process_one_work(), >> > we see the free stack is useless in KASAN report, it doesn't help >> > programmers to solve UAF on workqueue. The same may stand for times. >> > >> > This patchset improves KASAN reports by making them to have workqueue >> > queueing stack and timer stack information. It is useful for programmers >> > to solve use-after-free or double-free memory issue. >> > >> > Generic KASAN also records the last two workqueue and timer stacks and >> > prints them in KASAN report. It is only suitable for generic KASAN. > > Walter, did you mail v5? > Checking statuses of KASAN issues and this seems to be not in linux-next. > >> > [1]https://groups.google.com/g/syzkaller-bugs/search?q=%22use-after-free%22+process_one_work >> > [2]https://groups.google.com/g/syzkaller-bugs/search?q=%22use-after-free%22%20expire_timers >> >> How are these links useful for people who do not have a gurgle account? > > This is a public mailing list archive, so effectively the same way as > lore links ;) Just that it asked me to log in last time. That's why I wrote the above. Today it does not, odd. Thanks, tglx