From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id BB2D4158089 for ; Thu, 9 Nov 2023 18:00:06 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id F23152BC018; Thu, 9 Nov 2023 18:00:05 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [140.211.166.183]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C8ABA2BC018 for ; Thu, 9 Nov 2023 18:00:05 +0000 (UTC) Received: from oystercatcher.gentoo.org (oystercatcher.gentoo.org [148.251.78.52]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id A18B3335CB7 for ; Thu, 9 Nov 2023 18:00:04 +0000 (UTC) Received: from localhost.localdomain (localhost [IPv6:::1]) by oystercatcher.gentoo.org (Postfix) with ESMTP id D3596132A for ; Thu, 9 Nov 2023 18:00:01 +0000 (UTC) From: "Mike Pagano" To: gentoo-commits@lists.gentoo.org Content-Transfer-Encoding: 8bit Content-type: text/plain; charset=UTF-8 Reply-To: gentoo-dev@lists.gentoo.org, "Mike Pagano" Message-ID: <1699552780.4f42445d6ec6dc05fb74d5547df42572cef288e3.mpagano@gentoo> Subject: [gentoo-commits] proj/linux-patches:6.5 commit in: / X-VCS-Repository: proj/linux-patches X-VCS-Files: 0000_README 1805_mm-disable-CONFIG-PER-VMA-LOCK-by-def.patch X-VCS-Directories: / X-VCS-Committer: mpagano X-VCS-Committer-Name: Mike Pagano X-VCS-Revision: 4f42445d6ec6dc05fb74d5547df42572cef288e3 X-VCS-Branch: 6.5 Date: Thu, 9 Nov 2023 18:00:01 +0000 (UTC) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-commits@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply X-Archives-Salt: e4a0fba5-d7c6-43a4-84c2-854991134f6b X-Archives-Hash: 7e1bf8489b7e88a102133e21b4b88f91 commit: 4f42445d6ec6dc05fb74d5547df42572cef288e3 Author: Mike Pagano gentoo org> AuthorDate: Thu Nov 9 17:59:40 2023 +0000 Commit: Mike Pagano gentoo org> CommitDate: Thu Nov 9 17:59:40 2023 +0000 URL: https://gitweb.gentoo.org/proj/linux-patches.git/commit/?id=4f42445d Remove patch, as the issue is fixed Removed: 1805_mm-disable-CONFIG-PER-VMA-LOCK-by-def.patch Signed-off-by: Mike Pagano gentoo.org> 0000_README | 4 --- 1805_mm-disable-CONFIG-PER-VMA-LOCK-by-def.patch | 35 ------------------------ 2 files changed, 39 deletions(-) diff --git a/0000_README b/0000_README index 2dc5ce55..28310de0 100644 --- a/0000_README +++ b/0000_README @@ -99,10 +99,6 @@ Patch: 1700_sparc-address-warray-bound-warnings.patch From: https://github.com/KSPP/linux/issues/109 Desc: Address -Warray-bounds warnings -Patch: 1805_mm-disable-CONFIG-PER-VMA-LOCK-by-def.patch -From: https://lore.kernel.org/all/20230703182150.2193578-1-surenb@google.com/ -Desc: mm: disable CONFIG_PER_VMA_LOCK by default until its fixed - Patch: 2000_BT-Check-key-sizes-only-if-Secure-Simple-Pairing-enabled.patch From: https://lore.kernel.org/linux-bluetooth/20190522070540.48895-1-marcel@holtmann.org/raw Desc: Bluetooth: Check key sizes only when Secure Simple Pairing is enabled. See bug #686758 diff --git a/1805_mm-disable-CONFIG-PER-VMA-LOCK-by-def.patch b/1805_mm-disable-CONFIG-PER-VMA-LOCK-by-def.patch deleted file mode 100644 index c98255a6..00000000 --- a/1805_mm-disable-CONFIG-PER-VMA-LOCK-by-def.patch +++ /dev/null @@ -1,35 +0,0 @@ -Subject: [PATCH 1/1] mm: disable CONFIG_PER_VMA_LOCK by default until its fixed -Date: Mon, 3 Jul 2023 11:21:50 -0700 [thread overview] -Message-ID: <20230703182150.2193578-1-surenb@google.com> (raw) - -A memory corruption was reported in [1] with bisection pointing to the -patch [2] enabling per-VMA locks for x86. -Disable per-VMA locks config to prevent this issue while the problem is -being investigated. This is expected to be a temporary measure. - -[1] https://bugzilla.kernel.org/show_bug.cgi?id=217624 -[2] https://lore.kernel.org/all/20230227173632.3292573-30-surenb@google.com - -Reported-by: Jiri Slaby -Reported-by: Jacob Young -Fixes: 0bff0aaea03e ("x86/mm: try VMA lock-based page fault handling first") -Signed-off-by: Suren Baghdasaryan ---- - mm/Kconfig | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) - -diff --git a/mm/Kconfig b/mm/Kconfig -index 09130434e30d..de94b2497600 100644 ---- a/mm/Kconfig -+++ b/mm/Kconfig -@@ -1224,7 +1224,7 @@ config ARCH_SUPPORTS_PER_VMA_LOCK - def_bool n - - config PER_VMA_LOCK -- def_bool y -+ bool "Enable per-vma locking during page fault handling." - depends on ARCH_SUPPORTS_PER_VMA_LOCK && MMU && SMP - help - Allow per-vma locking during page fault handling. --- -2.41.0.255.g8b1d071c50-goog