| 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: Sat, 19 Jun 2010 10:17:01 +0200 From: Andi Kleen <andi@...stfloor.org> To: Michael Rubin <mrubin@...gle.com> Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org, linux-mm@...ck.org, jack@...e.cz, akpm@...ux-foundation.org, david@...morbit.com, hch@....de, axboe@...nel.dk Subject: Re: [PATCH 3/3] writeback: tracking subsystems causing writeback Michael Rubin <mrubin@...gle.com> writes: > > # cat /sys/block/sda/bdi/writeback_stats > balance dirty pages 0 > balance dirty pages waiting 0 > periodic writeback 92024 > periodic writeback exited 0 > laptop periodic 0 > laptop or bg threshold 0 > free more memory 0 > try to free pages 271 > syc_sync 6 > sync filesystem 0 That exports a lot of kernel internals in /sys, presumably read by some applications. What happens with the applications if the kernel internals ever change? Will the application break? It would be bad to not be able to change the kernel because of such an interface. -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