| 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: <899288751@web.de> Date: Sat, 05 Sep 2009 23:44:35 +0200 From: devzero@....de To: linux-kernel@...r.kernel.org Subject: block_dump - full path ? Hi, i came across the nice debugging feature sysctl vm.block_dump=1 which leaves information on read/write in dmesg for every process. Sep 5 20:11:15 neoware kernel: kjournald(423): WRITE block 155542512 on sda2 Sep 5 20:11:15 neoware kernel: kjournald(423): WRITE block 155542520 on sda2 Sep 5 20:11:15 neoware kernel: kjournald(423): WRITE block 155542528 on sda2 Sep 5 20:11:19 neoware kernel: pdflush(14): WRITE block 144498288 on sda2 Sep 5 20:11:19 neoware kernel: pdflush(14): WRITE block 144916496 on sda2 Sep 5 20:11:19 neoware kernel: pdflush(14): WRITE block 144917376 on sda2 Sep 5 20:11:19 neoware kernel: pdflush(14): WRITE block 144704600 on sda2 is it possible to log the full path of the process ? i assume it is a missing feature, correct ? what about adding full path support, to be enabled with "sysctl vm.block_dump=2" ? regards roland ______________________________________________________ GRATIS für alle WEB.DE-Nutzer: Die maxdome Movie-FLAT! Jetzt freischalten unter http://movieflat.web.de -- 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