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  linux-hardening  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:	Wed, 1 Dec 2010 22:00:12 -0800
From:	"Luck, Tony" <>
To:	Andrew Morton <>
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)

> 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.

I'll roll in fixes to address your other comments too.

Thanks for the review.

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