linux-kernel - Re: [RFC][6/11][MANUX] Kernel compatibility : directory hardlinks

lists.openwall.net		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 linux-cve-announce 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:	Tue, 15 Apr 2014 16:06:29 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Emmanuel Colbus <ecolbus@...ux.info>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [RFC][6/11][MANUX] Kernel compatibility : directory hardlinks

On Tue, Apr 15, 2014 at 03:43:01PM +0200, Emmanuel Colbus wrote:
> Now for something that has to do both with syscalls and filesystems...
> 
> My operating system relies heavily upon hardlinks, and, amongst others,
> directory hardlinks. (Yes, that's what my ext2l partitions are for. Not
> only, but this is part of it).
> 
> To allow distinguishing them from true directories, I've introduced a
> value S_IFDHL equal to 0130000, both for the file mode in stat(2) and
> for the type_entry field in the dirent structure, in getdents64(2).

Not without more information about what the value means, and what it
would be used for.  See my previous comments about why reserving code
points for random personal projects is not a something which is at all
scalable.

						- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/