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 A374D3A4537 for ; Tue, 31 Mar 2026 19:33:37 +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=1774985617; cv=none; b=qbuNqHaDGX9CXId7gDYHOhTiK3Gb5gEoWAUs3BMolj0airVbuYbrm2YNSF+fqbTnM0wfLxK4WEKJX7pTXFACVXs3Cc40/u3mzFtgBIgPeBx8/kntFwC3I7WKyWElzVyzTlVP+Z68uq1jzZgvBAJmry0IH5nVwA9klyryjtTIcQY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774985617; c=relaxed/simple; bh=tug8kCzckn5mE4rcWJDNZKZm/0J7JcgITmBTVRpC8Rs=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=PL6/3T3bh/ITAIsJbASIgvheM05vjyflo+KajALxLHNp1mL+Fy61BiR7OV29rzpg5mWS6FY3yxAs8FF5YOq6x59uf0c9N+Tr3Gc5WjsEHT3y5eLtobdFakYPLQVbSy9LDkchnclhqB99WSc8zgFNz0gWKYAbVv6a5a2fLwViF5I= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=YScw01Dz; 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="YScw01Dz" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 91E30C19423; Tue, 31 Mar 2026 19:33:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1774985617; bh=tug8kCzckn5mE4rcWJDNZKZm/0J7JcgITmBTVRpC8Rs=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=YScw01DzXCSKknGqi1JzAWPcaf99FWmdnvyQHdWCu4uRQZn6l2RPKexUVyZzINPI1 1tgkRhhyF+TVgHk2fyCLm4yT5C1FrS/P43iT8uyBvTopdvS6QbqTU81OVbe38L7eVk r2VzTCyYWuJ9MQEA47erEM6RMvWo4NmwDyROe/gu552wReg1B8UEf/hmr0oV0RkQrX G+Kb5m8mtr/6m+jYNH5G9d/RcrF/eTB87RAKGgbUB4Hsrl3pXfUgsQ6OKqU1jqwRP0 tTJ+ll0zux6XZxCKPcNXeV95U3IPIuzslUL+nbwaWu0rKpGx2yJEEps0Xnd1wJZ7cc SE9eH12Nwl3mg== From: Pratyush Yadav To: Pasha Tatashin Cc: rppt@kernel.org, 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 v3 04/10] liveupdate: Protect FLB lists with luo_register_rwlock In-Reply-To: <20260327033335.696621-5-pasha.tatashin@soleen.com> (Pasha Tatashin's message of "Fri, 27 Mar 2026 03:33:28 +0000") References: <20260327033335.696621-1-pasha.tatashin@soleen.com> <20260327033335.696621-5-pasha.tatashin@soleen.com> Date: Tue, 31 Mar 2026 19:33:33 +0000 Message-ID: <2vxzse9fhjzm.fsf@kernel.org> User-Agent: Gnus/5.13 (Gnus v5.13) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain On Fri, Mar 27 2026, 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) [...] -- Regards, Pratyush Yadav