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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 897FBC433F5 for ; Tue, 11 Oct 2022 01:20:21 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 230C26B0074; Mon, 10 Oct 2022 21:20:21 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 1E0B06B0075; Mon, 10 Oct 2022 21:20:21 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 081938E0002; Mon, 10 Oct 2022 21:20:21 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0016.hostedemail.com [216.40.44.16]) by kanga.kvack.org (Postfix) with ESMTP id EB3DC6B0074 for ; Mon, 10 Oct 2022 21:20:20 -0400 (EDT) Received: from smtpin20.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay08.hostedemail.com (Postfix) with ESMTP id C440A141079 for ; Tue, 11 Oct 2022 01:20:20 +0000 (UTC) X-FDA: 80006913000.20.D5FB6ED Received: from mail-oa1-f42.google.com (mail-oa1-f42.google.com [209.85.160.42]) by imf04.hostedemail.com (Postfix) with ESMTP id 636384001F for ; Tue, 11 Oct 2022 01:20:20 +0000 (UTC) Received: by mail-oa1-f42.google.com with SMTP id 586e51a60fabf-1326637be6eso14269455fac.13 for ; Mon, 10 Oct 2022 18:20:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=OBsU0GNWyfIKR8QJhJdP9cW2g/Tm8RsQ4/KCjmFrIcA=; b=ZYVC0As2dCkDlVVlxAaYR+Vf5j5NHKgM7FosPug9FKJ5N7poc0XVAWPatSsmLcJT2t hLId+80pcemqXzCYeaeUbvev6Avt0/+4+V1qVg8GDdlY0oReQH/zZH/TRufdS0zf7JZB /cReB6BKayZEApCnRjZzHWK4YpRpUlNMWvxIY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=OBsU0GNWyfIKR8QJhJdP9cW2g/Tm8RsQ4/KCjmFrIcA=; b=fKNLgd+cLq4dG7Rr/t2guDxHVN0RDBm747En9xqg0jUQmto3BgYGY6B+HebPZ4tMI8 0d66AAITh1tZ/iOVCQ/l1ZOhWohrTS1q7JcpmbeWuubfpUc2b8Y0xfaZDjhMWAmSVzQ4 a0islY2PM6divdyxHZn3wYu+qMaVm/4avpfK9h5eePVHCaovEC2BSMMv/mh8yNEqFWO/ wq4l2FSr0mDh48eVg1N5Ac9d7uMLZZScOfnwKtkLUGdAmmUTozo7+yTDaYKmcsXhCMiw BQcbGK7ASqay6chhXyxWQCOugYS+DCtUmdXPfrNBiLT1OzK24/NLIwUZeL3KmQaxiBJ5 Nk3w== X-Gm-Message-State: ACrzQf3G+n2GNG658eeRPOH0eJskO+N2NxMb1FECh3bHzz6bOXcu2tdm BbjlOYPW4IKMpPNLJhY2bTHXcb7Hj27WDg== X-Google-Smtp-Source: AMsMyM70MmvKqp2yFyhODVSxpXCTO2V0VcgR3N1iaOtGmfwSjEPLhddR+0LIpUucyZKfMJLlNjY28Q== X-Received: by 2002:a05:6870:179c:b0:136:3c63:3b86 with SMTP id r28-20020a056870179c00b001363c633b86mr8668240oae.131.1665451219139; Mon, 10 Oct 2022 18:20:19 -0700 (PDT) Received: from mail-oi1-f175.google.com (mail-oi1-f175.google.com. [209.85.167.175]) by smtp.gmail.com with ESMTPSA id g36-20020a9d12a7000000b006619fe836f9sm1528886otg.55.2022.10.10.18.20.16 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 10 Oct 2022 18:20:17 -0700 (PDT) Received: by mail-oi1-f175.google.com with SMTP id y72so7701075oia.3 for ; Mon, 10 Oct 2022 18:20:16 -0700 (PDT) X-Received: by 2002:a54:4899:0:b0:354:add8:52ab with SMTP id r25-20020a544899000000b00354add852abmr2158006oic.229.1665451216585; Mon, 10 Oct 2022 18:20:16 -0700 (PDT) MIME-Version: 1.0 References: <20221008132113.919b9b894426297de78ac00f@linux-foundation.org> In-Reply-To: <20221008132113.919b9b894426297de78ac00f@linux-foundation.org> From: Linus Torvalds Date: Mon, 10 Oct 2022 18:20:00 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [GIT PULL] MM updates for 6.1-rc1 To: Andrew Morton , Alexander Potapenko , Andrey Konovalov , Josh Poimboeuf , Peter Zijlstra Cc: mm-commits@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1665451220; a=rsa-sha256; cv=none; b=bam1squsjsPSi6D6AZ7Tfk3fsHGI+6/Mf3Dqojp3KpQiI+X1OImZ1X1KRnJbKU3BBKZbLr pBmoW8ZXo88B3EHD5qAk/bb0D7lyM7S65oigdMpwzE2Y/U0ipIoziSnkBzeixTgwYL10ao zcJtLu78luOECtdLi7qPAXa1EobS8mU= ARC-Authentication-Results: i=1; imf04.hostedemail.com; dkim=pass header.d=linux-foundation.org header.s=google header.b=ZYVC0As2; spf=pass (imf04.hostedemail.com: domain of torvalds@linuxfoundation.org designates 209.85.160.42 as permitted sender) smtp.mailfrom=torvalds@linuxfoundation.org; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1665451220; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=OBsU0GNWyfIKR8QJhJdP9cW2g/Tm8RsQ4/KCjmFrIcA=; b=xqUirdPnp+hMvDHIZtdegG4W35HIROHD4RBs3v7UaLx2hUO8oaY/zqnJsZX5DSw+52pDYr JJRI3CWJJgE6V+6ZSeZPJhQw3VsBLgRv7tMOA7Ec9uafFMRLGeje/ZUa36huT5wiHUH8wG 2oEJEUXpcLV162S/EGhcgtT6Cy5rTGU= Authentication-Results: imf04.hostedemail.com; dkim=pass header.d=linux-foundation.org header.s=google header.b=ZYVC0As2; spf=pass (imf04.hostedemail.com: domain of torvalds@linuxfoundation.org designates 209.85.160.42 as permitted sender) smtp.mailfrom=torvalds@linuxfoundation.org; dmarc=none X-Stat-Signature: i6r4qsyp96bi6pjj393mbczyptfhspbc X-Rspamd-Server: rspam08 X-Rspamd-Queue-Id: 636384001F X-Rspam-User: X-HE-Tag: 1665451220-289854 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 Sat, Oct 8, 2022 at 1:21 PM Andrew Morton wrote: > > Alexander Potapenko (43): > crypto: kmsan: disable accelerated configs under KMSAN Ok, so this conflicted pretty badly with the crypto tree having re-organized their Kconfig files. I channelled my inner Alexander the Great, and just cut the whole thing through by disabling all the architecture-accelerated crypto includes when KMSAN was enabled. But that's very different from your tree that disabled the options individually, so some KMSAN person should probably look around at it and decide whether some more subtle approach is called for. The other thing I notice from just doing a build is that I now get vmlinux.o: warning: objtool: kasan_report+0x12: call to stackleak_track_stack() with UACCESS enabled which may just be a "need to teach objtool this is ok", but I'm not seeing why it's now starting to happen. Maybe just code generation changed for some reason, or maybe it's just that config options ended up changing enough to expose this on my allmodconfig builds. Cc'ing people who may know better. This is just my reaction from doing the merge and test-build. There may or may not be more commentary once I've actually tried to boot into this thing. Linus