From: Steven Rostedt <rostedt@goodmis.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, Christian Brauner <brauner@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [LSF/MM TOPIC] Making pseudo file systems inodes/dentries more like normal file systems
Date: Sat, 27 Jan 2024 09:54:12 -0500 [thread overview]
Message-ID: <20240127095412.46b6e3dc@rorschach.local.home> (raw)
In-Reply-To: <CAOQ4uxjRxp4eGJtuvV90J4CWdEftusiQDPb5rFoBC-Ri7Nr8BA@mail.gmail.com>
On Sat, 27 Jan 2024 12:15:00 +0200
Amir Goldstein <amir73il@gmail.com> wrote:
> >
>
> I would like to attend the talk about what happened since we suggested
> that you use kernfs in LSFMM 2022 and what has happened since.
It was the lack of documentation to understand the concept it was
using. As I was very familiar with the way debugfs worked, I couldn't
map that same logic to how kernfs worked for what I wanted to do. I
remember spending a lot of time on it but just kept getting lost. I then
went to see if just modifying the current method with tracefs that was
like debugfs and things made a lot more sense. I guess the biggest
failure in that was my thinking that using the dentry as the main
handle was the proper way to do things, as supposed to being the exact
opposite. If I had known that from the beginning, I probably would have
approached it much differently.
> I am being serious, I am not being sarcastic and I am not claiming that
> you did anything wrong :)
Thanks ;-)
>
> Also ,please do not forget to also fill out the Google form:
>
> https://forms.gle/TGCgBDH1x5pXiWFo7
Crap, I keep forgetting about that form.
>
> So we have your attendance request with suggested topics in our spreadsheet.
Appreciate it.
-- Steve
next prev parent reply other threads:[~2024-01-27 14:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 15:48 [LSF/MM TOPIC] Making pseudo file systems inodes/dentries more like normal file systems Steven Rostedt
2024-01-26 1:24 ` Greg Kroah-Hartman
2024-01-26 1:50 ` Steven Rostedt
2024-01-26 1:59 ` Greg Kroah-Hartman
2024-01-26 2:40 ` Steven Rostedt
2024-01-26 14:16 ` Greg Kroah-Hartman
2024-01-26 15:15 ` Steven Rostedt
2024-01-26 15:41 ` Greg Kroah-Hartman
2024-01-26 16:44 ` Steven Rostedt
2024-01-27 10:15 ` Amir Goldstein
2024-01-27 14:54 ` Steven Rostedt [this message]
2024-01-27 14:59 ` James Bottomley
2024-01-27 18:06 ` Matthew Wilcox
2024-01-27 19:44 ` Linus Torvalds
2024-01-27 20:23 ` James Bottomley
2024-01-29 15:08 ` Christian Brauner
2024-01-29 15:57 ` Steven Rostedt
2024-01-27 20:07 ` James Bottomley
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=20240127095412.46b6e3dc@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).