[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240126081616.28c02f10@gandalf.local.home>
Date: Fri, 26 Jan 2024 08:16:16 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Christian Brauner <brauner@...nel.org>, Linus Torvalds
<torvalds@...ux-foundation.org>, Kees Cook <keescook@...omium.org>,
linux-kernel@...r.kernel.org, Masami Hiramatsu <mhiramat@...nel.org>, Mark
Rutland <mark.rutland@....com>, Mathieu Desnoyers
<mathieu.desnoyers@...icios.com>, Andrew Morton
<akpm@...ux-foundation.org>, Al Viro <viro@...iv.linux.org.uk>, Ajay Kaher
<ajay.kaher@...adcom.com>
Subject: Re: [for-linus][PATCH 1/3] eventfs: Have the inodes all for files
and directories all be the same
On Fri, 26 Jan 2024 09:07:06 +0100
Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> Hi Steven.
>
> On Thu, Jan 25, 2024 at 7:08 PM Steven Rostedt <rostedt@...dmis.org> wrote:
> > On Thu, 25 Jan 2024 13:07:31 -0500
> > Steven Rostedt <rostedt@...dmis.org> wrote:
> > > Actually, inodes isn't the biggest issue of tar, as tar *is* a common
> > > operation on tracefs.
> >
> > Correction. tar would be a common operation if it worked ;-)
>
> What would be needed to fix that? I regularly use tar on other virtual
> file systems (e.g. /sys/firmware/devicetree/), which works fine.
Looks like all /sys files have one page in size. I could change the default
file size to one page and it might work (if the inodes had different
numbers), as I don't see any format file greater than 4k.
This would fix the events for tar, but it couldn't do the same for tracing.
As some files don't actually have a size.
-- Steve
Powered by blists - more mailing lists