| 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
| ||
|
Message-ID: <a36005b50812192037g1380a997ycc87f600db18af0c@mail.gmail.com> Date: Fri, 19 Dec 2008 20:37:29 -0800 From: "Ulrich Drepper" <drepper@...il.com> To: "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org> Subject: st_mode bits What is the future of the bits beyond bit 15 in st_mode? Currently only 16 bits are used. There are old struct stat formats which have only 16 bit st_mode fields. Is this the limiting factor? I ask because I want to use one bit in glibc. If the future of the kernel calls for more than 16 bits in st_mode, can we agree on a bit (perhaps bit 31) to be reserved for userlevel? -- 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/
Powered by blists - more mailing lists