From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C880832E757; Tue, 14 Jul 2026 17:57:53 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784051875; cv=none; b=YhFTKcrSuH1Sg+BcUTonc9P7Q+A+2CgTzL+QSOvUTgm7zEwmr+CVJQMnabk3kFRnwey7EEEUzRGlOY0UuE6U+LIGt93IaqyX5wyGr0hK3P9KOcqo24O+mz+xxZcZrsXxtHnL4h1sQXvL0MEfcmxkCr8NQPI3ZtmHeb4XTlluvro= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784051875; c=relaxed/simple; bh=OI3JlDuLY07U0gR/Ke0Vick6BYegbcgNSuIJ8n4P2Dw=; h=Date:From:To:Cc:Subject:Message-Id:In-Reply-To:References: Mime-Version:Content-Type; b=oImAZL7MkL3ZHIjOrQob+aaLlNhb8WxVcI6C1Fgdlc6tTbzbXiwxPkRRc2PgMbb3mAeWQL1+vRJdYcuIwMcMmKhKMOPasKp2+GA/UZrHZgCRO//TRpjcJ84TQwOvcstqnCqSmD+pgYyJw5skmybJx811Aff5VdsZ2lVddMSXb6A= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux-foundation.org header.i=@linux-foundation.org header.b=Del5tMhz; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux-foundation.org header.i=@linux-foundation.org header.b="Del5tMhz" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 234151F000E9; Tue, 14 Jul 2026 17:57:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=korg; t=1784051873; bh=GZsCQFEgcn6EMOCDEWdLwPkfWWcQqzlkLED/YqdY1Tc=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=Del5tMhzu3youmLCKHjbgtPvdsDIH+7IGGFST8BzaPmqfbbkJZKJ/z7YuaAT/X/p7 YChgX7fSaBbak9aPutlauCQ1Jbkj4qG9n6iEshYriEkzHWNiPFv0rwct2vUBjwBQdh kaZUweQ5gxNphKPDgOzYUI91+awAsCTyJPp5rwvA= Date: Tue, 14 Jul 2026 10:57:51 -0700 From: Andrew Morton To: Stanislav Kinsburskii Cc: airlied@gmail.com, akhilesh@ee.iitb.ac.in, corbet@lwn.net, dakr@kernel.org, david@kernel.org, decui@microsoft.com, haiyangz@microsoft.com, jgg@ziepe.ca, kees@kernel.org, kys@microsoft.com, leon@kernel.org, liam@infradead.org, lizhi.hou@amd.com, ljs@kernel.org, longli@microsoft.com, lyude@redhat.com, maarten.lankhorst@linux.intel.com, mamin506@gmail.com, mhocko@suse.com, mripard@kernel.org, nouveau@lists.freedesktop.org, ogabbay@kernel.org, oleg@redhat.com, rppt@kernel.org, shuah@kernel.org, simona@ffwll.ch, skhan@linuxfoundation.org, surenb@google.com, tzimmermann@suse.de, vbabka@kernel.org, wei.liu@kernel.org, dri-devel@lists.freedesktop.org, linux-mm@kvack.org, linux-doc@vger.kernel.org, linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org, linux-rdma@vger.kernel.org Subject: Re: [PATCH v8 0/8] mm/hmm: Add mmap lock-drop support for userfaultfd-backed mappings Message-Id: <20260714105751.f45ec4c70702c222febdbf07@linux-foundation.org> In-Reply-To: References: <178371866223.900500.12312667138651735591.stgit@skinsburskii> <20260710151151.1e193eedd0cf2591ae392f76@linux-foundation.org> <20260710224950.53bcb43ce7e564f07a1f6a8c@linux-foundation.org> <20260713154535.7656b3a630e2f6f076b4e76e@linux-foundation.org> X-Mailer: Sylpheed 3.8.0beta1 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Precedence: bulk X-Mailing-List: linux-rdma@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit On Tue, 14 Jul 2026 09:09:51 -0700 Stanislav Kinsburskii wrote: > On Mon, Jul 13, 2026 at 03:45:35PM -0700, Andrew Morton wrote: > > On Mon, 13 Jul 2026 13:57:55 -0700 Stanislav Kinsburskii wrote: > > > > > > > I rebased this series on top of mm-new right before sending it out. > > > > > Should I have used a different branch? > > > > > > > > mm-new is good - Sashiko attempts that. But it's changing rapidly at > > > > this point in the development cycle. > > > > > > > > > > I’d like to send another revision addressing a few comments and also > > > replace the `max/max_t` check with something simpler. > > > > > > Which branch should I base it on so that Sashiko can apply it > > > successfully? > > > > mainline Linus would be safest. > > > > Looks like linux-next/master has been updated with the v8 of the series. That's because v8 is in mm.git's mm-unstable branch. > I have v9 with a few small fixes, but it is too late to send it out already? It's called "unstable" for a reason! Material in mm-unstable is still under review, test and the latest stages of development. Getting things finalized for movement into the non-rebasing mm-stable branch, then into mainline. So altering or replacing patchsets while they're in mm-unstable is perfectly OK and expected. > If it's not, then what should I base it on? Well it's a bit tricky to replace a series when it's in mm-unstable. One can do a git-checkout of the commit which precedes the v8 series. Or base on current Linus mainline, which usually works out. Sending little fixup patches against what's presently in mm-unstable also works. I'll queue each one immediately behind the patch which it alters then squash them into their parent patch before moving the series into mm-stable. A third alternative is for me to drop v8 from mm-unstable, then you wait until that has propagated onto the servers or into linux-next, then base on that. This approach is OK but I kinda unprefer it because there's a bit of latency and it makes it harder for me to prepare my "here's how v9 altered mm.git" summaries. Which would you prefer?