linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: Samiullah Khawaja <skhawaja@google.com>
Cc: rppt@kernel.org, akpm@linux-foundation.org, linux-mm@kvack.org,
	 linux-kernel@vger.kernel.org, dmatlack@google.com,
	pratyush@kernel.org
Subject: Re: [PATCH v3 03/10] liveupdate: Protect file handler list with rwsem
Date: Mon, 30 Mar 2026 15:32:05 -0400	[thread overview]
Message-ID: <CA+CK2bC5B0NNi=C=E1EryURhoR5_EZVgU45t1cfzFeiVpcoNQw@mail.gmail.com> (raw)
In-Reply-To: <acqnQ64U8Cxst-ce@google.com>

> >Because liveupdate file handlers will no longer hold a module reference
> >when registered, we must ensure that the access to the handler list is
> >protected against concurrent module unloading.
>
> Nit: Here we make an assumption that the file (and flb) handler
> lifecycle is bound with the module lifecycle. It is a fair assumption,
> but maybe this can be documented somewhere?

That is true, we can certainly add this to Doc. comment. This could be
done as a follow-up change if needed.

> >+      up_read(&luo_register_rwlock);
>
> We took the read lock here when running can_preserve, but then we use
> the fh without taking the lock later before calling file_preserve. This
> is safe since the module reference is taken and fh will not go away
> (based on the assumption I mentioned above). Maybe add a comment here
> that documents this assumption.

Sure, if I respin this series, I will add a comment; otherwise, it
will be a follow-up change along with updating the documentation
comment as you suggested above.

Thanks,
Pasha


  reply	other threads:[~2026-03-30 19:32 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
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 [this message]
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='CA+CK2bC5B0NNi=C=E1EryURhoR5_EZVgU45t1cfzFeiVpcoNQw@mail.gmail.com' \
    --to=pasha.tatashin@soleen.com \
    --cc=akpm@linux-foundation.org \
    --cc=dmatlack@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pratyush@kernel.org \
    --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