All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ali Nasrolahi <a.nasrolahi01@gmail.com>
To: Raka Gunarto <rakagunarto@gmail.com>
Cc: Richard <richard_siegfried@systemli.org>,
	kernelnewbies@kernelnewbies.org
Subject: Re: Seeking guidance on detecting mount point inactivity
Date: Mon, 6 Jul 2026 10:27:47 +0330	[thread overview]
Message-ID: <aktMsIIP3jSG1nio@zephyr> (raw)
In-Reply-To: <CACUOwm+TSzS0u8VQF7Zbdf7es5OsdRh5V94EvdD5WcMK_EF8Tg@mail.gmail.com>

On 26/07/05 05:34PM, Raka Gunarto wrote:
> Are your workloads okay to wait indefinitely on a call to open()? I
> believe you can use the fanotify permission events (FAN_OPEN_PERM) to
> queue the call and then poll for active handles until they close.
> After the maintenance operations then respond FAN_ALLOW to the
> requests in the queue.

To be honest, I don't have a concrete idea of how different workloads
would behave if an `open()` were blocked for an extended period, but I
think they should be alright.

Could you elaborate a bit on what you mean by polling the active
handles?  My understanding is that, regardless of the enforcement
mechanism (fanotify, eBPF, or something else) the challenges of
determining that a mount has actually become inactive (and remained so
for the grace period) are still there, right? same ebpf issues, what if
the daemon didn't count the existing handles or somehow crashes and lose
the count. These challenges are common; or am I overlooking something?

--Ali

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      reply	other threads:[~2026-07-06  6:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-25 14:37 Seeking guidance on detecting mount point inactivity Ali Nasrolahi
2026-06-30 14:21 ` Richard
2026-07-03  9:05   ` Ali Nasrolahi
2026-07-03  9:54     ` Raka Gunarto
2026-07-05  5:04       ` Ali Nasrolahi
2026-07-05 16:34         ` Raka Gunarto
2026-07-06  6:57           ` Ali Nasrolahi [this message]

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=aktMsIIP3jSG1nio@zephyr \
    --to=a.nasrolahi01@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=rakagunarto@gmail.com \
    --cc=richard_siegfried@systemli.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.