From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BBFB1C433EF for ; Wed, 20 Oct 2021 22:29:16 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 31B64611CC for ; Wed, 20 Oct 2021 22:29:16 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 31B64611CC Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linux-foundation.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kvack.org Received: by kanga.kvack.org (Postfix) id AAF00900002; Wed, 20 Oct 2021 18:29:15 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id A5F316B0072; Wed, 20 Oct 2021 18:29:15 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 94E4A900002; Wed, 20 Oct 2021 18:29:15 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0060.hostedemail.com [216.40.44.60]) by kanga.kvack.org (Postfix) with ESMTP id 835FB6B006C for ; Wed, 20 Oct 2021 18:29:15 -0400 (EDT) Received: from smtpin03.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay02.hostedemail.com (Postfix) with ESMTP id 4453A2FE15 for ; Wed, 20 Oct 2021 22:29:15 +0000 (UTC) X-FDA: 78718257870.03.7937ADC Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by imf27.hostedemail.com (Postfix) with ESMTP id 9790A7000081 for ; Wed, 20 Oct 2021 22:29:13 +0000 (UTC) Received: by mail.kernel.org (Postfix) with ESMTPSA id F36716056B; Wed, 20 Oct 2021 22:29:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1634768952; bh=jRHi18PfO4NBozNbrNBvNRggK2ZyxPV2M2RhSxhsXMU=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=TEnlDxKO4pPNEPA8gMkZMBGcRHi0pPKo1l5f/n3ejSwPQs+QQF0oFWcxHlefY//GH rcg/twsI8uuY/cEonHRFx/BIrlhZwfaRvfZ4tVriO9cpl1MDkAnQD2HW/bPFKh3Fpd xuNvX08dOoJlR76MvWo/YNj6TrqKypUwXxEFUdmo= Date: Wed, 20 Oct 2021 15:29:09 -0700 From: Andrew Morton To: Marco Elver Cc: Kuan-Ying Lee , Andrey Ryabinin , Alexander Potapenko , Andrey Konovalov , Dmitry Vyukov , Catalin Marinas , Will Deacon , Matthias Brugger , chinwen.chang@mediatek.com, yee.lee@mediatek.com, nicholas.tang@mediatek.com, kasan-dev@googlegroups.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-mediatek@lists.infradead.org Subject: Re: [PATCH v3] kasan: add kasan mode messages when kasan init Message-Id: <20211020152909.2ea34f8f0c0d70d8b245b234@linux-foundation.org> In-Reply-To: References: <20211020094850.4113-1-Kuan-Ying.Lee@mediatek.com> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 9790A7000081 X-Stat-Signature: thqsjkte3j4bhbpd8rscreor16ugzz9u Authentication-Results: imf27.hostedemail.com; dkim=pass header.d=linux-foundation.org header.s=korg header.b=TEnlDxKO; dmarc=none; spf=pass (imf27.hostedemail.com: domain of akpm@linux-foundation.org designates 198.145.29.99 as permitted sender) smtp.mailfrom=akpm@linux-foundation.org X-Rspamd-Server: rspam01 X-HE-Tag: 1634768953-440561 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Wed, 20 Oct 2021 11:58:26 +0200 Marco Elver wrote: > On Wed, 20 Oct 2021 at 11:48, Kuan-Ying Lee wrote: > > > > There are multiple kasan modes. It makes sense that we add some messages > > to know which kasan mode is when booting up. see [1]. > > > > Link: https://bugzilla.kernel.org/show_bug.cgi?id=212195 [1] > > Signed-off-by: Kuan-Ying Lee > > Reviewed-by: Marco Elver > > Thank you. > > Because this is rebased on the changes in the arm64 tree, and also > touches arch/arm64, it probably has to go through the arm64 tree. That would be OK, as long as it doesn't also have dependencies on pending changes elsewhere in the -mm tree. To solve both potential problems, I've queued it in -mm's post-linux-next section, so it gets sent to Linus after both -mm and arm have merged up.