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 X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BF32CC433B4 for ; Sun, 2 May 2021 18:05:00 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 4F3AC61352 for ; Sun, 2 May 2021 18:05:00 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4F3AC61352 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=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 673076B0036; Sun, 2 May 2021 14:04:59 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 623146B006E; Sun, 2 May 2021 14:04:59 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 4C3C96B0070; Sun, 2 May 2021 14:04:59 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0089.hostedemail.com [216.40.44.89]) by kanga.kvack.org (Postfix) with ESMTP id 30CB16B0036 for ; Sun, 2 May 2021 14:04:59 -0400 (EDT) Received: from smtpin14.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay02.hostedemail.com (Postfix) with ESMTP id D8D176D8A for ; Sun, 2 May 2021 18:04:58 +0000 (UTC) X-FDA: 78097067076.14.B32564F Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by imf29.hostedemail.com (Postfix) with ESMTP id A67A13D0 for ; Sun, 2 May 2021 18:04:53 +0000 (UTC) Received: by mail.kernel.org (Postfix) with ESMTPSA id 30177610FC; Sun, 2 May 2021 18:04:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1619978697; bh=RMzxlhg5QnpgDwVktb697u84AkdnLgHnGdDSv9o3yBU=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=Q6WEJIYBKovoNnHZxvObOu5DPzjnDlWTwOqTbRlXaCyteXYZD7PblL1yf4OIfJrxA zHpziI9+aEg+zFoRDoI4exyixvDaG99JN4g3oCgfcRIGXmf2rQf9sG6Uy6HuQnsSTA IhoBG15CM9za6cSNKMZPTK9p+IEhBEsjK2xan0js= Date: Sun, 2 May 2021 11:04:56 -0700 From: Andrew Morton To: Linus Torvalds Cc: Stephen Rothwell , Andrey Konovalov , Andrey Ryabinin , Dmitry Vyukov , Marco Elver , Alexander Potapenko , Linux-MM , mm-commits@vger.kernel.org Subject: Re: [patch 148/178] kasan: detect false-positives in tests Message-Id: <20210502110456.238c3e175d35e4a6ce8a6088@linux-foundation.org> In-Reply-To: References: <20210429225251.02b6386d21b69255b4f6c163@linux-foundation.org> <20210430060049.FrKVS3ZER%akpm@linux-foundation.org> 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-Server: rspam05 X-Rspamd-Queue-Id: A67A13D0 Authentication-Results: imf29.hostedemail.com; dkim=pass header.d=linux-foundation.org header.s=korg header.b=Q6WEJIYB; dmarc=none; spf=pass (imf29.hostedemail.com: domain of akpm@linux-foundation.org designates 198.145.29.99 as permitted sender) smtp.mailfrom=akpm@linux-foundation.org X-Stat-Signature: ffaahye1doecqcr3hcm95rren5mn8bap Received-SPF: none (linux-foundation.org>: No applicable sender policy available) receiver=imf29; identity=mailfrom; envelope-from=""; helo=mail.kernel.org; client-ip=198.145.29.99 X-HE-DKIM-Result: pass/pass X-HE-Tag: 1619978693-690909 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 Fri, 30 Apr 2021 11:32:43 -0700 Linus Torvalds wrote: > This patch is untested garbage that doesn't even compile. Sorry, I fat-fingered a thing and used gcc-9, which disables CONFIG_KASAN. > Use the previous release as a base (ie in this case 5.12) Not a problem for the first batch of patches, but what base do I use for the second and succeeding batches? > If you have patches in > your patch-series that depend on stuff that comes in this merge > window, just drop them - or at least don't send them to me. Maybe 10% of the patches I carry are based on changes which are in linux-next. Things like - tree-wide renames which need to catch other developers adding instances of the old name. They'll pop up in third-party testing and I do a last-minute grep to find these. - changes which I've worked with other developers to stage things in that order. - removal of duplicated includes for which I need to do a last-minute check that nobody has gone and removed the other include. - new syscalls which would generate a ton of conflicts with new syscalls in other trees. - right now I'm carrying a pile of little spelling fixes. I stage these after linux-next to find out whether other tree maintainers have independently merged the same patches, or partially similar ones from others. - etc. I send this sort of material to you very late in the merge window, after the prerequisites have been merged up.