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 lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 40811EB64DD for ; Tue, 11 Jul 2023 11:02:42 +0000 (UTC) Authentication-Results: lists.ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=vB76sJ66; dkim-atps=neutral Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4R0dJ02bNdz3c5P for ; Tue, 11 Jul 2023 21:02:40 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=vB76sJ66; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=kernel.org (client-ip=139.178.84.217; helo=dfw.source.kernel.org; envelope-from=leon@kernel.org; receiver=lists.ozlabs.org) Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) (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 lists.ozlabs.org (Postfix) with ESMTPS id 4R0dH05Rg0z301r for ; Tue, 11 Jul 2023 21:01:48 +1000 (AEST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (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 dfw.source.kernel.org (Postfix) with ESMTPS id A7E9C61477; Tue, 11 Jul 2023 11:01:46 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 55DC2C433C7; Tue, 11 Jul 2023 11:01:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1689073306; bh=R05i0tfIilRVHzTS9Y6rvcMfdBq0WFxNA/CtDRe9kk4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=vB76sJ66UWbSFxqdwf7J5SwQ7MdPBoPk4RK9avcVbGxISO6cLmi8tu422q2aRHNRb XSiGx9a08oyMinnRV4gFgj2enU1kyNlVB0Atn9FfjOz2PAdT0Arse2cR/UMwIq9uEV +BDDjI0ZOxha16mUE5TbYZd9/bhO8444m4dJbCD/Eq0aUGQJROHd4RdJvSQSgYRyVF nQUsgsaa9CbO4JC54oVkjyO48OYqRSh4e4cldVtSgmFmpyrQfqZ3ecDjzFNEknvtuz OJkBU/CFCRhPoPCDLbCeGfkwOSVJ2avvOo+6ibWOqwsZTaFLSw9dr2ty8M3swOBF2U 4B0fNwUdBnCyA== Date: Tue, 11 Jul 2023 14:01:41 +0300 From: Leon Romanovsky To: Vlastimil Babka Subject: Re: [PATCH v4 00/33] Per-VMA locks Message-ID: <20230711110141.GN41919@unreal> References: <20230227173632.3292573-1-surenb@google.com> <20230711103541.GA190975@unreal> <53676850-539f-2813-d55d-a8bc0ec88092@suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53676850-539f-2813-d55d-a8bc0ec88092@suse.cz> X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: michel@lespinasse.org, joelaf@google.com, songliubraving@fb.com, mhocko@suse.com, Sachin Sant , leewalsh@google.com, david@redhat.com, peterz@infradead.org, bigeasy@linutronix.de, peterx@redhat.com, dhowells@redhat.com, linux-mm@kvack.org, edumazet@google.com, jglisse@google.com, punit.agrawal@bytedance.com, sergeyy@nvidia.com, will@kernel.org, arjunroy@google.com, Linux kernel regressions list , chriscli@google.com, dave@stgolabs.net, minchan@google.com, gal@nvidia.com, x86@kernel.org, hughd@google.com, willy@infradead.org, gurua@google.com, mingo@redhat.com, rientjes@google.com, axelrasmussen@google.com, kernel-team@android.com, maorg@nvidia.com, ranro@nvidia.com, michalechner92@googlemail.com, soheil@google.com, paulmck@kernel.org, jannh@google.com, liam.howlett@oracle.com, regressions@leemhuis.info, shakeelb@google.com, drort@nvidia.com, luto@kernel.org, gthelen@google.com, Laurent Dufour , Suren Baghd asaryan , linux-arm-kernel@lists.infradead.org, posk@google.com, lstoakes@gmail.com, peterjung1337@gmail.com, linuxppc-dev@lists.ozlabs.org, kent.overstreet@linux.dev, linux-kernel@vger.kernel.org, idok@nvidia.com, hannes@cmpxchg.org, Andrew Morton , tatashin@google.com, mgorman@techsingularity.net, rppt@kernel.org Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Tue, Jul 11, 2023 at 12:39:34PM +0200, Vlastimil Babka wrote: > On 7/11/23 12:35, Leon Romanovsky wrote: > > > > On Mon, Feb 27, 2023 at 09:35:59AM -0800, Suren Baghdasaryan wrote: > > > > <...> > > > >> Laurent Dufour (1): > >> powerc/mm: try VMA lock-based page fault handling first > > > > Hi, > > > > This series and specifically the commit above broke docker over PPC. > > It causes to docker service stuck while trying to activate. Revert of > > this commit allows us to use docker again. > > Hi, > > there have been follow-up fixes, that are part of 6.4.3 stable (also > 6.5-rc1) Does that version work for you? I'll recheck it again on clean system, but for the record: 1. We are running 6.5-rc1 kernels. 2. PPC doesn't compile for us on -rc1 without this fix. https://lore.kernel.org/all/20230629124500.1.I55e2f4e7903d686c4484cb23c033c6a9e1a9d4c4@changeid/ 3. I didn't see anything relevant -rc1 with "git log arch/powerpc/mm/fault.c". Do you have in mind anything specific to check? Thanks