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 7EB06EB64DC for ; Tue, 11 Jul 2023 17:14:17 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id C19316B0072; Tue, 11 Jul 2023 13:14:16 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id BC8D96B0074; Tue, 11 Jul 2023 13:14:16 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id A91166B0075; Tue, 11 Jul 2023 13:14:16 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0012.hostedemail.com [216.40.44.12]) by kanga.kvack.org (Postfix) with ESMTP id 9A1DF6B0072 for ; Tue, 11 Jul 2023 13:14:16 -0400 (EDT) Received: from smtpin30.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay06.hostedemail.com (Postfix) with ESMTP id 52D58B008B for ; Tue, 11 Jul 2023 17:14:16 +0000 (UTC) X-FDA: 80999979312.30.194FD7A Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by imf01.hostedemail.com (Postfix) with ESMTP id 94ADE40026 for ; Tue, 11 Jul 2023 17:14:13 +0000 (UTC) Authentication-Results: imf01.hostedemail.com; dkim=pass header.d=kernel.org header.s=k20201202 header.b=Gr3AhEta; spf=pass (imf01.hostedemail.com: domain of leon@kernel.org designates 139.178.84.217 as permitted sender) smtp.mailfrom=leon@kernel.org; dmarc=pass (policy=none) header.from=kernel.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1689095653; 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=Tn1gQ43Mi0ArYWOm73gfSKNQxfV1Kyt7g2IJ+FItMDc=; b=PaCJ2HKX/VjI1Ld+kwWttLShMODy25k9dJsQ1rUSNzPUq9VbL/Wv5DZaVqhJt15kQqWAOU uv3u6POR4VQ7EjfClRAf5KmHxxZXx38+9cFYnUdVoFddWjlYQA4zv383MmfEqb8/FI9q0P A9E21kcvI7RwmQebe9MY3ks0VT7QTnE= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1689095653; a=rsa-sha256; cv=none; b=d0nN/uDU2REEH9mJM4f3rh3H6t2XxS7/CdCmwRb7wRa598AudKP3Vq7saHmLyemFNUcKUR 07cdQGBz5oWUvj7eMPgi9SJBQ+1JF/tnpLVjmLFvQoyETeq940Tbkyucbo/jU4w0ue/rT/ HdilmOX2dSZ0vp+aQxqFO3LhuCTMDNo= ARC-Authentication-Results: i=1; imf01.hostedemail.com; dkim=pass header.d=kernel.org header.s=k20201202 header.b=Gr3AhEta; spf=pass (imf01.hostedemail.com: domain of leon@kernel.org designates 139.178.84.217 as permitted sender) smtp.mailfrom=leon@kernel.org; dmarc=pass (policy=none) header.from=kernel.org 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 A710F61589; Tue, 11 Jul 2023 17:14:12 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4CCCDC433C8; Tue, 11 Jul 2023 17:14:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1689095652; bh=86IlMeB02kfIELN4JFOeqEXOrye+aqoKhFqCQG7VOig=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Gr3AhEtagw1brAmYmnAbs73gciLhmKWUnyV6CMkTfay98QySCMTe8OlSZzlG09SVd 1Qjm5UA00h0gKH82z50orU4V4fCXQDEEDxtSRDs1Jqqn1f5NQANaT7S8pptqZkCUIA snYd3QSYyCg5y+0NeQb/JZGuQCOzftElGNfruNfCHt3//CU6U18v8afZqq43UvKRZx rYI16JuEjTSp/Nwh/Zui5wammS6a+qu67zO9glI/OzUAyUltRw30ypgk6ukm3le5wi PtegWv/Zw4cITTVeb3HsNGVBkBd1tSAyCuS390q9wDkxbpJWvpIySwyNyjRYuXsWIM Lu7fHWCwg79CA== Date: Tue, 11 Jul 2023 20:14:07 +0300 From: Leon Romanovsky To: Suren Baghdasaryan Cc: Vlastimil Babka , Laurent Dufour , Sachin Sant , Andrew Morton , michel@lespinasse.org, jglisse@google.com, mhocko@suse.com, hannes@cmpxchg.org, mgorman@techsingularity.net, dave@stgolabs.net, willy@infradead.org, liam.howlett@oracle.com, peterz@infradead.org, paulmck@kernel.org, mingo@redhat.com, will@kernel.org, luto@kernel.org, songliubraving@fb.com, peterx@redhat.com, david@redhat.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, gurua@google.com, arjunroy@google.com, soheil@google.com, leewalsh@google.com, posk@google.com, michalechner92@googlemail.com, linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org, linuxppc-dev@lists.ozlabs.org, x86@kernel.org, linux-kernel@vger.kernel.org, kernel-team@android.com, regressions@leemhuis.info, Linux kernel regressions list , maorg@nvidia.com, gal@nvidia.com, ranro@nvidia.com, drort@nvidia.com, idok@nvidia.com, sergeyy@nvidia.com Subject: Re: [PATCH v4 00/33] Per-VMA locks Message-ID: <20230711171407.GU41919@unreal> References: <20230227173632.3292573-1-surenb@google.com> <20230711103541.GA190975@unreal> <53676850-539f-2813-d55d-a8bc0ec88092@suse.cz> <20230711110141.GN41919@unreal> <20230711110945.GO41919@unreal> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Stat-Signature: uwsenxb7iga7qr3rigip1ajsb65gkfup X-Rspamd-Server: rspam10 X-Rspamd-Queue-Id: 94ADE40026 X-Rspam-User: X-HE-Tag: 1689095653-573341 X-HE-Meta: U2FsdGVkX1+RK/jbpivTsemM3y9yilEq9IseOY0Ofux0wSbarF/yFyIW86z4EQC4W0osyWQHX83rcxj5c2hJacQ9yRB2syXWPhzfgC9uooVt7+Y5GPC88GXu+bLvxRaxux5SWvjhqeoYN25AdiBXGkZucxQzUtAgc5qzRBU3ECwjE3jxODM/odKlvsY2likihUPsFfE5Wn98e9NQA3LyZ++1KgILb01J6mJusv249P8+jemKD+pDPyk02o5tySyZnygim9wQpiW5Xgw7QIbInpDsCpbzodLs/nFLCE4y0zzXczlUlitEIiSHcB8LDnGisQLFbpaJhDs6+OfPCwQR+Ha+tJ88pbOI2wtbyhax/LdUBT5JY0fqyaHMu3a5NOagF1neDoNyukF1usU5CUqt9Lag/mpB1z7kwy53KkaNzgvOY0Uu+DfX4dMDPzlUnIKZrmA56cjWnFmXfFLU+ODsDl5C7+IZOLPY2xuf7d4uws1Ed1UHj88WBuZ04Qkz7kwOV0msgrfNOYsNs1B+fwyVmu3/LfQZsItDV0XW9zZLyYlXb0ia1PP7vDt3BowqgD+aQJXHWZDpgJzms9Q+xTPYPhlpZVMpglXyvhv8N75xc0vIyyT42Zvr3jTQZhFv0IKbx9YWj8UH9yc5x/k4ogGG4S6rbBPXk4jKzIkm5LKZkTG1Nibs4ZSlZ5md4Bg1Pyp6YG7q0PR6urPdhfebTb8JpHW4Jpd36Xqzb7nzewUeXx3Ram7QzwtiNOO78b1xBDZ4jE3uKtPRDvQyuXr7e3Yec1HxMwBDl963s/QCLuRIcpD+E7sPpLT0tWjd2xEXrBCHVX14EV+8LkLU9+j8HsVoy3yWxIJgFP0W6rpbOfWC1jrib1fW2BmIobnftzfmTokVi+po1LZpZvarIFrUwMUGBX07IIBjjAVdAxBVPj5h5Yu4oHa4IvpAXrnd7Odm+0GoYHwqoAN0Ek5E1Y3VBxJ tDrtvDGN kiCZS9zO1DoVYtzXKtyHn2n8P5QSzQG8xJZ50kCjw1zwacEL0Ns1FqpFr9urGVUwWPy1boPUTiosoq3LSgry3YwNfX7pn2lSEoed0UBc7GF35oAPPH1ngfvuedLDxMoLgTyY3870yqi6nnT2vGaFeATNGXP4fYQkjQ4Wa8NJDf3Ba4dy+b1DKdifOgOjTFwgv3JOuqoZIWBLKDcBrU8j6F8KAPcwB6tolBlXvQEdbdEWjb2c1LqJXh1RENOPxVZC8nL+DMgOcbxYvroq9rrMGTGHEV7NxnZXBeGDuDkrzQn1oKnKvgSasZIMssmGUZOyGXWM3L0ENYyniWoZWkC8kXKKgDs84wuIe013F6qynpW9IgobWAGfncE5TBlrxoPtmpXfWxoNYwRiXpt4= 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 Tue, Jul 11, 2023 at 09:35:13AM -0700, Suren Baghdasaryan wrote: > On Tue, Jul 11, 2023 at 4:09 AM Leon Romanovsky wrote: > > > > On Tue, Jul 11, 2023 at 02:01:41PM +0300, Leon Romanovsky wrote: > > > 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/ > > > > Ohh, I see it in -rc1, let's recheck. > > Hi Leon, > Please let us know how it goes. Once, we rebuilt clean -rc1, docker worked for us. Sorry for the noise. > > > > > > 3. I didn't see anything relevant -rc1 with "git log arch/powerpc/mm/fault.c". > > The fixes Vlastimil was referring to are not in the fault.c, they are > in the main mm and fork code. More specifically, check for these > patches to exist in the branch you are testing: > > mm: lock newly mapped VMA with corrected ordering > fork: lock VMAs of the parent process when forking > mm: lock newly mapped VMA which can be modified after it becomes visible > mm: lock a vma before stack expansion Thanks > > Thanks, > Suren. > > > > > > > Do you have in mind anything specific to check? > > > > > > Thanks > > > > > > > -- > > To unsubscribe from this group and stop receiving emails from it, send an email to kernel-team+unsubscribe@android.com. > >