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: Wed, 7 May 2008 23:06:49 +0800 From: "rae l" <crquan@...il.com> To: "Matthew Wilcox" <matthew@....cx> Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: It's time to hack on dentry_stat? On Wed, May 7, 2008 at 10:51 PM, Matthew Wilcox <matthew@....cx> wrote: > You have to not break: > > $ cat /proc/sys/fs/dentry-state > 122104 115846 45 0 0 0 But why? for some applicatioins? The struct dentry_stat can be modified to have only two useful fields, and let the other four printed with 0, I have greped age_limit, that's also not used anymore, why we should let it keep 45? Or Is there some historical reason? Or just consider /proc/sys/fs/dentry-state as a binary application interface? -- 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