[lkml]   [2024]   [Jan]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] eventfs: Have inodes have unique inode numbers
On Fri, 26 Jan 2024 at 13:26, Steven Rostedt <> wrote:
> I'd be happy to change that patch to what I originally did before deciding
> to copy get_next_ino():
> unsigned int tracefs_get_next_ino(int files)
> {
> static atomic_t next_inode;
> unsigned int res;
> do {
> res = atomic_add_return(files + 1, &next_inode);
> /* Check for overflow */
> } while (unlikely(res < files + 1));
> return res - files;

Still entirely pointless.

If you have more than 4 billion inodes, something is really really wrong.

So why is it ten lines instead of one?

Dammit, this is a number that NOBODY HAS SHOWN IS EVEN WORTH EXISTING

So no. I'm not taking this. End of discussion. My point stands: I want
this filesystem *stabilized*, and in s sane format.

Look to *simplify* things. Send me patches that *remove* complexity,
not add new complexity that you have zero evidence is worth it.

Face it, eventfs isn't some kind of "real filesystem". It shouldn't
even attempt to look like one.

If somebody goes "I want to tar this thiing up", you should laugh in
their face and call them names, not say "sure, let me whip up a
50-line patch to make this fragile thing even more complex".


 \ /
  Last update: 2024-01-26 22:36    [W:0.030 / U:0.172 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site