| 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
| ||
|
Date: Mon, 21 Jun 2010 12:32:23 +0200 From: Andi Kleen <andi@...stfloor.org> To: Aleksandr Koltsoff <aleksandr.koltsoff@...s.fi> Cc: Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org Subject: Re: RFC: Exporting NOCMTIME to userspace > While this might solve the performance aspect of the problem, it will > only migitate the reliability aspect with NANDs, since the inodes will > eventually be flushed anyway (thus causing irreversible wear). As long as you don't run out of memory it will happen very rarely. Completely elimintating inode writes is not a good goal imho. Iff you don't want inodes at all then perhaps consider using a LVM volume or similar instead of a file system. > Also, a tunable like you're suggesting would affect all files on a > single filesystem, instead of just a subset of files. Having an option > to "disable" m/ctime updates per file would be optimal in our case, > since we're talking about several years of runtime with the use case. > There are other issues with rrdtool which make this hard, but those are > all solvable without kernel modifications. Yes, but the nice thing is that the semantics are the same, so unless you crash you won't really notice. -Andi -- ak@...ux.intel.com -- Speaking for myself only. -- 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