lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 2 Dec 2010 02:12:16 -0800
From:	Andrew Morton <>
To:	"Luck, Tony" <>
Cc:	"" <>,
	"" <>,
	"" <>,
	"" <>, "" <>,
	"Huang, Ying" <>,
	Borislav Petkov <>,
	David Miller <>,
	Alan Cox <>,
	Jim Keniston <>,
	Kyungmin Park <>,
	Geert Uytterhoeven <>
Subject: Re: [RFC] persistent store (version 2) (part 1 of 2)

On Wed, 1 Dec 2010 22:00:12 -0800 "Luck, Tony" <> wrote:

> > filenames refer to files!  And lo, that's what we have here.  A
> > filesystem!  The files are created by the kernel and are read and
> > unlinked by userspace.
> >
> > So why not implement this whole thing as a proper filesystem?
> ...
> > Wait.  It *is* a filesystem.
> ...
> > So why can't I remove these "records" with rm?
> Because I tried to use /sys for this and couldn't find a
> way to get notified about "unlink".  Alan Cox called this
> bit "daft" in v1 (and I agreed with him). Peter Anvin gave
> me some pointers on how easy this would be to do as a real
> filesystem ... so v3 will be out in a little while with
> this insanity removed.

OK.  Yes, the correct answer is usually "create a new filesystem
driver" ;)


gad, there are over 200 register_filesystem() callsites.

One thing which does leap out of the v2 implementation is the hardwired
assumption that there is one store kernel-wide.  I suppose that's OK as
a version-1 implementation detail thing, but we should avoid hardwiring
that assumption into the presentation of v1's userspace interfaces.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists