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 C4D7DC63797 for ; Tue, 17 Jan 2023 15:16:52 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 5877F6B0078; Tue, 17 Jan 2023 10:16:52 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 537576B007B; Tue, 17 Jan 2023 10:16:52 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 4259F6B007D; Tue, 17 Jan 2023 10:16:52 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0010.hostedemail.com [216.40.44.10]) by kanga.kvack.org (Postfix) with ESMTP id 36AF66B0078 for ; Tue, 17 Jan 2023 10:16:52 -0500 (EST) Received: from smtpin07.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay06.hostedemail.com (Postfix) with ESMTP id AE6A5AB002 for ; Tue, 17 Jan 2023 15:16:51 +0000 (UTC) X-FDA: 80364643422.07.CE049C2 Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by imf05.hostedemail.com (Postfix) with ESMTP id C6BB7100017 for ; Tue, 17 Jan 2023 15:16:49 +0000 (UTC) Authentication-Results: imf05.hostedemail.com; dkim=pass header.d=suse.com header.s=susede1 header.b=L8FayK7S; dmarc=pass (policy=quarantine) header.from=suse.com; spf=pass (imf05.hostedemail.com: domain of mhocko@suse.com designates 195.135.220.29 as permitted sender) smtp.mailfrom=mhocko@suse.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1673968610; 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=sbKnvqVmnloOJo8HuU71AavisB7MfzGt7Jm/2K4Gntk=; b=LZY5lmRcUib6PS3hdRayLqRAJTBTsE1SyhVz6dr7X+zwZvaezH11LUXuWolKY3+zKLZ7hY bblTuE0uvCLhsol8UB55jt9qmDsDLVNIKGD7dLhsVgqK2drI0ZsEyDCsi8FCa0IeQY4npH RmYfYOErhxSzeIv3vdcdmJL72yoyqMo= ARC-Authentication-Results: i=1; imf05.hostedemail.com; dkim=pass header.d=suse.com header.s=susede1 header.b=L8FayK7S; dmarc=pass (policy=quarantine) header.from=suse.com; spf=pass (imf05.hostedemail.com: domain of mhocko@suse.com designates 195.135.220.29 as permitted sender) smtp.mailfrom=mhocko@suse.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1673968610; a=rsa-sha256; cv=none; b=2VETjHcZ7VF2Gg7ZfwjsE3ld7i/4F4VhF0DehQEcZyV0m4CT6Mb6ZnLB029v7T1A6w0ZHT P5t9n3mm/4/TN5xZXtjwFDXWirGtBVrjYAI87oN1ldJU7YnknT9MoqloeBm6B/Jc/tRUeH e4o2eXcd9et+Mef5QQj3Q1rSLnoed8M= Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out2.suse.de (Postfix) with ESMTPS id 4AE766892D; Tue, 17 Jan 2023 15:16:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1673968608; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=sbKnvqVmnloOJo8HuU71AavisB7MfzGt7Jm/2K4Gntk=; b=L8FayK7SEImi09Gn0nDikdyr4xu02WwvC2ahHV7p0kuKZX7Q+cRdDKjni+/ewcuaHQ5T0b Xn8wfQg5p+XnZ1SOy4Ud0+LCTzpv42KKhKu+cv3JVr8p4V1KSdWsVyDbuUjRaX8oSaiPKn BNiG8VEKSrvA6jY77OladKujxKFstkc= Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 1D33C1390C; Tue, 17 Jan 2023 15:16:48 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id q9KbBuC7xmMcRgAAMHmgww (envelope-from ); Tue, 17 Jan 2023 15:16:48 +0000 Date: Tue, 17 Jan 2023 16:16:47 +0100 From: Michal Hocko To: Suren Baghdasaryan Cc: akpm@linux-foundation.org, michel@lespinasse.org, jglisse@google.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, laurent.dufour@fr.ibm.com, paulmck@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, axelrasmussen@google.com, joelaf@google.com, minchan@google.com, jannh@google.com, shakeelb@google.com, tatashin@google.com, edumazet@google.com, gthelen@google.com, gurua@google.com, arjunroy@google.com, soheil@google.com, hughlynch@google.com, leewalsh@google.com, posk@google.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 Subject: Re: [PATCH 17/41] mm/mmap: move VMA locking before anon_vma_lock_write call Message-ID: References: <20230109205336.3665937-1-surenb@google.com> <20230109205336.3665937-18-surenb@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230109205336.3665937-18-surenb@google.com> X-Rspamd-Queue-Id: C6BB7100017 X-Rspamd-Server: rspam09 X-Rspam-User: X-Stat-Signature: 8g68h64pbzna7s5dntd57pi1yt1kgc64 X-HE-Tag: 1673968609-724060 X-HE-Meta: U2FsdGVkX1+VQeUc/JFRx2LWrDaiVJKUU6Bgnd+HKH/V2iqndYyjJPzjeq0p9fQpuz5brHRKYgriprxIcS3nQE7heKXWhQsBZaXQkJTwXuIcCO2udPKac+yLanbiVn+aDw5TXqtGjz9hJFfWGoJLs6iYTSTdw7K28242iHU7DRu3+iIj8TT3aclbn8l4vulRejWY2lXUjdaYjPtbi5+0hOQMhInpJobvaOMIhBxiD04lQR894TAxKHTpzETDmFTuW3P8cgOmWtP9275t4Pfgia8iQnlhN1dnpdZQWVLcVEuvvKXv2ObjCXOzZA5YL218/iZvPszwY2YbvqNsjG4zkMMOzybmzilFQMjCKviecaiHch6Vx2sZWdFD5Z96EF9Rch0xUK79ZxCVdJbnUvnwSsbsfG3jq9xRK2tnZOASMgWyjtUEOkDojJyq3f4travgmoAZDfzPnNUT2W1I7g2B2c6DaMlk1Yadd9/Chd+aFAPHGd+O8V0RE2ZK6LJQpS3J4JUlWP32ongL+8LEApPtWJpB0sy1qMsFCwmMDaay08SmsTy+Nh9A5MeB9v+jQ3jGscyYZnxb+FM2L5rTaoS4ACPM+2GW4KH2B2MhAcajGcpvzBA8jdqZdJQmWx6jRe4WpHMLoJmYQesq08xHYB6JsU5aqU9F7Ro3vdo7XnIG7HXt5YGGgHJ9hqcARZ+VvMHnIRhqZ3I1Ziwe8a6Dmt69ZwAlZiyVEip/a09ZUnWCKiSpziyyUuhLzvYCKzdS8J4k3mARgbSt++lbriKmalL4cYcW6lk/xPtDirT0Tzf8hsx88v0aCLPEEUaI+LQUxXLEAG3fb70hatYZCzmuYYIPwaL10nW/NEREq9tUf5cchNjP9ZbAomC6JYYN4IN+UuwtVemZVmh+4v3dOJyHhlfOMWV4y2KfMKVU 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 Mon 09-01-23 12:53:12, Suren Baghdasaryan wrote: > Move VMA flag modification (which now implies VMA locking) before > anon_vma_lock_write to match the locking order of page fault handler. Does this changelog assumes per vma locking in the #PF? -- Michal Hocko SUSE Labs