From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 A47CB3DA7F6 for ; Wed, 15 Apr 2026 15:26:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776266802; cv=none; b=FlsmZmUzHtss/gTQJcvxfHBjyUJbbFfJsz8/x90atg+RDpTih/EWbWKhHkVIvOxlPlhSO/C0vEaEsUyFj1yzVpEPlwGmQnaPSxCQ/bnlyHj35nbN0PRQ/WSIzYOTmwgECson8nd7wSrYyECZ4qBirM7naQtFIf6FOjuLyFMby9Y= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1776266802; c=relaxed/simple; bh=xGKBplUfNTwIfUx1ToWl6ViqiUPi9OO2hAKBdFxJN8k=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=hbGJFcbBCaR4XGyLjMyRentR2kbf9rnq+gDP3p5Zk3QWiAtIlknVM+gdQW01kzg5VBSywov0UqrBWitvgEeAR+w+F4sRDlQgf3hEb4r7N5w0YDH1Jwc4kE3nQrHfVuUftJA+xrAMmWv89U0pOUX0NTBN8xPjooFEIeuATJ9SQSA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=L+AeWokG; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="L+AeWokG" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7AE1FC2BCB0; Wed, 15 Apr 2026 15:26:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1776266802; bh=xGKBplUfNTwIfUx1ToWl6ViqiUPi9OO2hAKBdFxJN8k=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=L+AeWokGRrLG6FzvYhX1dd2PA2f/c986Hsq8WdFarRpaZq0uIz7pqJBAJdp4piuCF XxK/IxC7RpG4QcYQMJiy3/yRVz5s1BJHrYr5oz3oYBe/WL+T0mz5/b9iWS+9RHTUXq JTrnqp8zBURLH1gayPrKaoob2j6eDa50eJLfZW/bbAfx647yS9jBLMT6g4rb6jiHz9 +wK/qlrbbdwRFYeCmWdikLjRq4W4dD3ndh1L3nH+lT6EMXO5lZ7nZCcknj6oNFRxpV yWR/qu/D2RJcXB1Up1CZw5HSNHbgR3zuWVuT8W7aazSHyetgwmk+nFTJr1nTfhVFOQ SApD8hPIfaX3g== Date: Wed, 15 Apr 2026 18:26:37 +0300 From: Mike Rapoport To: Pasha Tatashin Cc: akpm@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, dmatlack@google.com, pratyush@kernel.org, skhawaja@google.com Subject: Re: [PATCH v4 04/11] liveupdate: Protect FLB lists with luo_register_rwlock Message-ID: References: <20260413185127.128180-1-pasha.tatashin@soleen.com> <20260413185127.128180-5-pasha.tatashin@soleen.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260413185127.128180-5-pasha.tatashin@soleen.com> On Mon, Apr 13, 2026 at 06:51:20PM +0000, Pasha Tatashin wrote: > Because liveupdate FLB objects will soon drop their persistent module > references when registered, list traversals must be protected against > concurrent module unloading. > > To provide this protection, utilize the global luo_register_rwlock. > It protects the global registry of FLBs and the handler's specific > list of FLB dependencies. > > Read locks are used during concurrent list traversals (e.g., during > preservation and serialization). Write locks are taken during registration > and unregistration. > > Signed-off-by: Pasha Tatashin > Reviewed-by: Pratyush Yadav (Google) Reviewed-by: Mike Rapoport (Microsoft) > --- > include/linux/liveupdate.h | 1 + > kernel/liveupdate/luo_flb.c | 14 ++++++++++++++ > 2 files changed, 15 insertions(+) -- Sincerely yours, Mike.