public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Yadav <pratyush@kernel.org>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: Pratyush Yadav <pratyush@kernel.org>,
	 rppt@kernel.org, akpm@linux-foundation.org,  linux-mm@kvack.org,
	linux-kernel@vger.kernel.org,  dmatlack@google.com,
	 skhawaja@google.com
Subject: Re: [PATCH v3 02/10] liveupdate: Synchronize lazy initialization of FLB private state
Date: Tue, 31 Mar 2026 19:22:23 +0000	[thread overview]
Message-ID: <2vxz1pgziz2o.fsf@kernel.org> (raw)
In-Reply-To: <CA+CK2bDFidSZQ+UevEXPgfF2BWkN1AWkb2iRWGxUNV2iLpJGXA@mail.gmail.com> (Pasha Tatashin's message of "Tue, 31 Mar 2026 12:41:54 -0400")

On Tue, Mar 31 2026, Pasha Tatashin wrote:

> On Tue, Mar 31, 2026 at 6:38 AM Pratyush Yadav <pratyush@kernel.org> wrote:
>>
>> On Fri, Mar 27 2026, Pasha Tatashin wrote:
>>
>> > The luo_flb_get_private() function, which is responsible for lazily
>> > initializing the private state of FLB objects, can be called
>> > concurrently from multiple threads. This creates a data
>> > race on the 'initialized' flag and can lead to multiple executions of
>> > mutex_init() and INIT_LIST_HEAD() on the same memory.
>> >
>> > Introduce a static spinlock (luo_flb_init_lock) local to the function
>> > to synchronize the initialization path. Use smp_load_acquire() and
>> > smp_store_release() for memory ordering between the fast path and the
>> > slow path.
>> >
>> > Signed-off-by: Pasha Tatashin <pasha.tatashin@soleen.com>
>>
>> Reviewed-by: Pratyush Yadav <pratyush@kernel.org>
>
> Thank you.
>
>>
>> But... wouldn't it be a whole lot simpler if we introduce a
>> DEFINE_LUO_FLB() and get rid of luo_flb_get_private() entirely:
>
> We are planning some updates to this code in the near future:
>
> 1. David Matlack will send a patch in the next version of VFIO LUO
> preservation series to add liveupdate_flb_put_incoming() so that
> caller can protect from race with release of the last FD release that
> will also release FLB.
> This change will increment FLB 'count' not only when FH uses it, but
> also when the object is being accessed.
>
> 2. After I plan to convert 'count' to use kref, and also decouble init
> and liveupdate_flb_get_incoming(), this will allow to access FLB
> object with interrupts disabled, as requested by Sami for the IOMMU
> work. I think, that while working on this 2nd change, we can also do
> some clean-ups if necessary.

Okay, makes sense. I really think this initialization of private state
on first use is ugly and it should be gotten rid of. So please, whenever
you plan to do this refactor, include something like the static
initialization I mentioned.

>
> Pasha
>
>>
>> #define DEFINE_LUO_FLB(_name, _ops, _compatible)                        \
>>         struct liveupdate_flb _name = {                                 \
>>                 .ops = _ops,                                            \
>>                 .compatible = _compatible,                              \
>>                 .private = {                                            \
>>                         .list = LIST_HEAD_INIT(_name.private.list),     \
>>                         .list = LIST_HEAD_INIT(_name.private.list),     \
>>                         / ...
>>                 },                                                      \
>>         }
>>
>> I can't get sparse to work so not sure if I need some special syntax to
>> initialize stuff in .private, but I reckon we can get something working.
>>

-- 
Regards,
Pratyush Yadav

  reply	other threads:[~2026-03-31 19:22 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-27  3:33 [PATCH v3 00/10] liveupdate: Fix module unloading and unregister API Pasha Tatashin
2026-03-27  3:33 ` [PATCH v3 01/10] liveupdate: Safely print untrusted strings Pasha Tatashin
2026-03-27 13:16   ` Pasha Tatashin
2026-03-31  9:40     ` Pratyush Yadav
2026-03-31  9:50   ` Pratyush Yadav
2026-03-31 16:35     ` Pasha Tatashin
2026-03-27  3:33 ` [PATCH v3 02/10] liveupdate: Synchronize lazy initialization of FLB private state Pasha Tatashin
2026-03-31 10:38   ` Pratyush Yadav
2026-03-31 16:41     ` Pasha Tatashin
2026-03-31 19:22       ` Pratyush Yadav [this message]
2026-03-31 19:38         ` Pasha Tatashin
2026-03-27  3:33 ` [PATCH v3 03/10] liveupdate: Protect file handler list with rwsem Pasha Tatashin
2026-03-30 16:48   ` Samiullah Khawaja
2026-03-30 19:32     ` Pasha Tatashin
2026-03-31 19:24   ` Pratyush Yadav
2026-03-27  3:33 ` [PATCH v3 04/10] liveupdate: Protect FLB lists with luo_register_rwlock Pasha Tatashin
2026-03-31 19:33   ` Pratyush Yadav
2026-03-27  3:33 ` [PATCH v3 05/10] liveupdate: Defer FLB module refcounting to active sessions Pasha Tatashin
2026-03-30 16:56   ` Samiullah Khawaja
2026-03-30 19:28     ` Pasha Tatashin
2026-04-02 16:21   ` Pratyush Yadav
2026-03-27  3:33 ` [PATCH v3 06/10] liveupdate: Remove luo_session_quiesce() Pasha Tatashin
2026-04-02 16:27   ` Pratyush Yadav
2026-03-27  3:33 ` [PATCH v3 07/10] liveupdate: Auto unregister FLBs on file handler unregistration Pasha Tatashin
2026-04-03 10:17   ` Pratyush Yadav
2026-03-27  3:33 ` [PATCH v3 08/10] liveupdate: Remove liveupdate_test_unregister() Pasha Tatashin
2026-04-03 10:20   ` Pratyush Yadav
2026-03-27  3:33 ` [PATCH v3 09/10] liveupdate: Make unregister functions return void Pasha Tatashin
2026-03-27 14:41   ` Pasha Tatashin
2026-04-03 10:41   ` Pratyush Yadav
2026-03-27  3:33 ` [PATCH v3 10/10] liveupdate: Defer file handler module refcounting to active sessions Pasha Tatashin
2026-03-27 17:14   ` Andrew Morton
2026-04-03 10:42   ` Pratyush Yadav
2026-03-27 17:24 ` [PATCH v3 00/10] liveupdate: Fix module unloading and unregister API Andrew Morton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2vxz1pgziz2o.fsf@kernel.org \
    --to=pratyush@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=dmatlack@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pasha.tatashin@soleen.com \
    --cc=rppt@kernel.org \
    --cc=skhawaja@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox