linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Cc: lsf-pc <lsf-pc@lists.linux-foundation.org>,
	Jan Kara <jack@suse.cz>,  Christian Brauner <brauner@kernel.org>,
	Josef Bacik <josef@toxicpanda.com>,
	 Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
Subject: [LSFMM BoF] fanotify HSM update
Date: Thu, 9 May 2024 11:44:58 +0300	[thread overview]
Message-ID: <CAOQ4uxij0aF1JMkqqVKfG2OS1eufZcbtLQF22GTgMi+rSSaCeg@mail.gmail.com> (raw)
In-Reply-To: <1715243542-29509-mlmmj-76fd78f9@vger.kernel.org>

FYI, I plan to do an fanotify HSM [1] BoF at LSFMM.
I haven't put it on the agenda yet.
I'll schedule it closer to or during the summit.

Talking points:
- Progress since last year (untangle vfs permission hooks [2])
- Next round of planned patches (pre-content permission events [3])
- Open API questions: dealing with the death of HSM service [4]
- Use cases for HSM and the FUSE passthrough alternative [5]

Thanks,
Amir.


[1] https://github.com/amir73il/fsnotify-utils/wiki/Hierarchical-Storage-Management-API
[2] https://lore.kernel.org/linux-fsdevel/20240105-vfs-rw-9b5809292b57@brauner/
[3] https://lore.kernel.org/linux-fsdevel/20231207123825.4011620-1-amir73il@gmail.com/
[4] https://lore.kernel.org/linux-fsdevel/CAOQ4uxiW6dxz8w3muHxogbPuNGa0cdubr_YSti1Jp97LLehaYg@mail.gmail.com/
[5] https://lore.kernel.org/linux-fsdevel/e9aac186-7935-485e-b067-e80ff19743dc@dorminy.me/

           reply	other threads:[~2024-05-09  8:45 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1715243542-29509-mlmmj-76fd78f9@vger.kernel.org>]

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=CAOQ4uxij0aF1JMkqqVKfG2OS1eufZcbtLQF22GTgMi+rSSaCeg@mail.gmail.com \
    --to=amir73il@gmail.com \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=josef@toxicpanda.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=sweettea-kernel@dorminy.me \
    /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;
as well as URLs for NNTP newsgroup(s).