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 A514DEB64DA for ; Thu, 6 Jul 2023 00:30:44 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 3AB8B8D0002; Wed, 5 Jul 2023 20:30:44 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 35B8F8D0001; Wed, 5 Jul 2023 20:30:44 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 2221A8D0002; Wed, 5 Jul 2023 20:30:44 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id 10F138D0001 for ; Wed, 5 Jul 2023 20:30:44 -0400 (EDT) Received: from smtpin21.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay01.hostedemail.com (Postfix) with ESMTP id D69B41C8EFB for ; Thu, 6 Jul 2023 00:30:43 +0000 (UTC) X-FDA: 80979306366.21.2EC833A Received: from mail-yb1-f182.google.com (mail-yb1-f182.google.com [209.85.219.182]) by imf07.hostedemail.com (Postfix) with ESMTP id 1228740007 for ; Thu, 6 Jul 2023 00:30:41 +0000 (UTC) Authentication-Results: imf07.hostedemail.com; dkim=pass header.d=google.com header.s=20221208 header.b=iPWV8L1j; dmarc=pass (policy=reject) header.from=google.com; spf=pass (imf07.hostedemail.com: domain of surenb@google.com designates 209.85.219.182 as permitted sender) smtp.mailfrom=surenb@google.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1688603442; 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:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=fDNtb8VGNsWJMd94B1yvjb9baMo04ogysNrDvAUSWkk=; b=ve7+cYhPNoXt4M4OSTTALL61DswWY8Juw7sLNAF35BjV3+CVbSAvibDpOZKskluHDe3DBV uCEkkhQrx1BkPxU78qBHxHlpegoD3zWCk9cCxXz929xONx3fEuRyxfMCFHv2MrK9oIp3t/ GL52AP+4WihBOwKTOuMKWwzGnvKCBBw= ARC-Authentication-Results: i=1; imf07.hostedemail.com; dkim=pass header.d=google.com header.s=20221208 header.b=iPWV8L1j; dmarc=pass (policy=reject) header.from=google.com; spf=pass (imf07.hostedemail.com: domain of surenb@google.com designates 209.85.219.182 as permitted sender) smtp.mailfrom=surenb@google.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1688603442; a=rsa-sha256; cv=none; b=ELmrj2kBfZGs9/39DAbFOJnbKG4BrZRn6EWzDcAY3KilP5VpDDYddrht6AwoKuzZINFUdn RkihGR3GvIM/toLYiONhgmweHu3jYTgxtk4Ty+/kOlc83j7hsfsbxGlP/dZgvFLDI7Rfy9 W1lOyTafyyqFKsFa09ddl3B7B4hkMq0= Received: by mail-yb1-f182.google.com with SMTP id 3f1490d57ef6-c5e67d75e0cso78246276.2 for ; Wed, 05 Jul 2023 17:30:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1688603441; x=1691195441; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=fDNtb8VGNsWJMd94B1yvjb9baMo04ogysNrDvAUSWkk=; b=iPWV8L1jyHGFjgPG1e5DkKfQtY3x/CGt89+fMJ/bu3j/1cV87OyziFgyMwLBr32FHf eJAll/hxbFiau5yzj/0Xxv1XL4TrpqOek4oJPr+TWFqHfOyLAo4Ezfs6GXxb8GDL3nTT rraj5yM6rOwTWTUhoQ6EFOEPYXTzSqqYg6EqUuuh3uhasSCtxx6M7pB8nzeUxR9IEkai es1f/vIFQs89by4IxE+GjuqppQ5L53M6CJWf/ZaQdW0DW3FBm7fBzko1gzm6lkd3KqcN n0EHMop9F4f72B6zSYgFWgSG/QvKNC3uvRcsaZXjFndUnGrWi8n8AVKq5CKgDTEQR4px wpDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688603441; x=1691195441; h=content-transfer-encoding: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=fDNtb8VGNsWJMd94B1yvjb9baMo04ogysNrDvAUSWkk=; b=jT5dgqdv46Wk4lztot4IsjwaC7lZrbBwjnG3PpAl5e+Npn4l4aERtPHdjy0dW6T092 janilzIS5iCg9TbPm72apHVqLHD3sjuPMp6PG1LBPCh1LEV4XceuXJ1V3MPkbs3WJpqz jM66QMcbWeZvVUOpoSewHCHrTkBMNtt5VZnsTRFjutQN/ZnW0IMjP4/5RqINyHfJijRv g6JFZGql37sC4m6vbJoXT7LRFMLhQBIgiEjkC9hezWxSfY97Kpo4cEjoWcDFvgNUymo5 harJ3hblqnYQb9tRiP7cQgsYmOECWaIdvhkUUvPns3hFKclozY7Fyd/ievv33/u5QUWh mgGQ== X-Gm-Message-State: ABy/qLaWZZok/ThCDBWLzjrdRayPyk1qL+TLTeI/h2iKSBVJYxnmtcKr UtwXMsclVY5JmSBPPMZMB4ftFfuZ/R3iJBU5RBBgaw== X-Google-Smtp-Source: APBJJlGTkJWTILVgZXDRlL1p0hLqObb6Qq5zIIPhh84UNi8OaQy1jTvMQiQf1KyO7Y1YLXWRj8pKQK81+RRrsDVVNdk= X-Received: by 2002:a25:98c6:0:b0:c0b:7483:5cdb with SMTP id m6-20020a2598c6000000b00c0b74835cdbmr342231ybo.35.1688603440921; Wed, 05 Jul 2023 17:30:40 -0700 (PDT) MIME-Version: 1.0 References: <20230705171213.2843068-1-surenb@google.com> <20230705171213.2843068-3-surenb@google.com> <3cdaa7d4-1293-3806-05ce-6b7fc4382458@redhat.com> <20230705172424.e505f5013bfdf44543d9c6be@linux-foundation.org> In-Reply-To: <20230705172424.e505f5013bfdf44543d9c6be@linux-foundation.org> From: Suren Baghdasaryan Date: Wed, 5 Jul 2023 17:30:29 -0700 Message-ID: Subject: Re: [PATCH v3 2/2] mm: disable CONFIG_PER_VMA_LOCK until its fixed To: Andrew Morton Cc: Peter Xu , David Hildenbrand , jirislaby@kernel.org, jacobly.alt@gmail.com, holger@applied-asynchrony.com, hdegoede@redhat.com, michel@lespinasse.org, jglisse@google.com, mhocko@suse.com, vbabka@suse.cz, hannes@cmpxchg.org, mgorman@techsingularity.net, dave@stgolabs.net, willy@infradead.org, liam.howlett@oracle.com, peterz@infradead.org, ldufour@linux.ibm.com, paulmck@kernel.org, mingo@redhat.com, will@kernel.org, luto@kernel.org, songliubraving@fb.com, dhowells@redhat.com, hughd@google.com, bigeasy@linutronix.de, kent.overstreet@linux.dev, punit.agrawal@bytedance.com, lstoakes@gmail.com, peterjung1337@gmail.com, rientjes@google.com, chriscli@google.com, axelrasmussen@google.com, joelaf@google.com, minchan@google.com, rppt@kernel.org, jannh@google.com, shakeelb@google.com, tatashin@google.com, edumazet@google.com, gthelen@google.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 1228740007 X-Rspam-User: X-Rspamd-Server: rspam02 X-Stat-Signature: kcyi99ywew48jbz1cikk41t49n7r7bdo X-HE-Tag: 1688603441-118738 X-HE-Meta: U2FsdGVkX1+FPKSFyyxSm6oP1LIVZCgu5gwTlXVl/m8jROOipgZ5DcH3ARn4TqZEYIEOLARQ3cDKJBXYa3yvb7xT1NovFo7w5iM6vs7wgLx2LuiVVivbG/El+SPQTE24kXZX6hJmO8ED7K66cDk8JZR0jLTRW7n+7sL7KqG0OWRb+iWyEVggsLYjGfSvhwggCU4gykj1n8bNESjacE8+JoJDr23u9KXGBnpjJPoExaprEWmFQZTLzvBspF30Z3Iy1ytwx3GaZCJETL+eFGLGBpTsEfNW6VhRROgNkCy3+w1cDy6X4IEQg5YHU4d16VgxsVRKdGONTKLcX33dG4EFhiV5QhEEbqJsah0DlJPFyJLayQwStrFMFr90NnRkQeaTz5nNZ5d+boquPtN/R+wN8DWbO8m4ocXz0B28slHbdxeM9vgowSArVDq3sekmqUiI4d94iyd1Q+pVKqLz5nrhtzvHpetJ0XUP9i68qFe2zhxxrRDjPS0fDPESYehCInOB4b2+tHzgsfTBZ4C2dk5hH7K+Kb0C9bQDnCPQM3pMLh7Dp2HYei8giJ7swd3E1Xrf/i3ML1CTMi4VwYaXhEoJW0jgppelb/VwP/BzxL2WPgjGFrmWLBBlxRYFNPrln43+/zfrMEsBkpEZaPw5YAp+jMd5qbRpdpRMcBEm7f1r5s6WgvSo2kOzye/lbctH8HBjhlnIqQWlBL7TCgFID3jkiZNsjvoYLKmUdz+ydM+bQnN/9usInrWeKCxDBWfQAzkOvKqIzaL2VTMONkQ0TUs+X+HAA50mlVy2eQFY4S4zKglZxcHCJ1vK86feqX33SKFCuNhqYauXKWR9T11ByicPy/uStgYqkAZknnUHeQc2EuBecXQCkQWBLNh1M0d7R/WYwPpc8ZOQ2cLmnd8ouXyAQK6OztrC7OqMtcbHFgk9lys3yCaHA64n7J6ITdsBqYQF3Cn/g/ok+KFSJ+p+vTz Uw7Kikh9 ezw3z/CvU7SMK8qQ9+H9l7169XHfLHZdGHVGHGWEB9FfWFrkAArtJ3RP5JIt2mrhAFtfJ3xrMdNPTC0BZoM82wL+mGyswQKJdG5pYd1gkPPQc37foCkVIpaMXqw/KuRDwzRvzfXnh+ireDYFWD1jwcJ0HeM/7XyNl3s6VLBS2EveBZVPEc5PIo4ZcsfJAhP1AsKh6jICIMoYzZ+jf9Wd5sUtHR4r/LcQghsbiIyj6izJLg0BkCmZ6BVsdUGnM5bZlhMOgGZAwiRXRYV6LxGY8IynjgUJ/1e3eVWnN4uWvqEDkQ5OD94KWuUG+w3yBNon5hRSh8GKE2/nkVjqYPJsie6VD+7m8xpf98Oc7i3QkYXkTb4BdqtwzJq7anYx1v3dWmINfOUr/vJPWLxqtaoIyvDJddp+AnSBSWrudehS2EzPUXQ1YfduBvDSptqH8BegYesvi6Th/wkaotSA= 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, Jul 5, 2023 at 5:24=E2=80=AFPM Andrew Morton wrote: > > On Wed, 5 Jul 2023 13:33:26 -0700 Suren Baghdasaryan = wrote: > > > I was hoping we could re-enable VMA locks in 6.4 once we get more > > confirmations that the problem is gone. Is that not possible once the > > BROKEN dependency is merged? > > I think "no". By doing this we're effectively backporting a minor > performance optimization, which isn't a thing we'd normally do. In that case, maybe for 6.4 we send the fix and only disable it by default without marking BROKEN? That way we still have a way to enable it if desired? >