| 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: <87r6j26rsj.fsf@olafdietsche.de> Date: Wed, 07 Nov 2007 15:42:20 +0100 From: Olaf Dietsche <olaf+list.linux-kernel@...fdietsche.de> To: Jan Kara <jack@...e.cz> Cc: Olaf Dietsche <olaf+list.linux-kernel@...fdietsche.de>, linux-kernel@...r.kernel.org Subject: Re: [PATCH] 2.6.23: Filesystem capabilities 0.17 Jan Kara <jack@...e.cz> writes: > On Thu 01-11-07 23:22:51, Olaf Dietsche wrote: >> >> The bits are stored in a sparse file named /.capabilities in the >> directory of the mount point, where the corresponding executable >> lives. The inode number of the file is the index into this file. > Thanks for explanation. I guess I should warn you a bit :) Quota stores > it's data (which are in a certain sence filesystem metadata) in regular > files and believe me it brings some unexpected complexity. Especially > avoiding deadlocks with journaled filesystems was quite complex for quotas > (you cannot call filesystem write function when a transaction is already > started or deadlocks can happen). Thanks for this hint. I will investigate this, if time permits. To be honest, I use and test with ext2 exclusively. > I guess with capabilities you need to write to the file only in some > special situations but still you could have problems with that. Regards, Olaf. - 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