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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 11 Nov 2009 18:10:15 -0500 From: fche@...hat.com (Frank Ch. Eigler) To: Arjan van de Ven <arjan@...radead.org> Cc: Jeff Garzik <jeff@...zik.org>, Wu Fengguang <fengguang.wu@...el.com>, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org, Christoph Hellwig <hch@...radead.org>, Al Viro <viro@...IV.linux.org.uk>, mingo@...e.hu, Frederic Weisbecker <fweisbec@...il.com>, auke-jan.h.kok@...el.com Subject: Re: [PATCH] vfs: Add a trace point in the mark_inode_dirty function Arjan van de Ven <arjan@...radead.org> writes: > [...] ok let me rephrase that. What would a user DO with this inode > number information, given that the filename is already passed on; > what additional useful, not-infinitely-hard-to-get piece of > information [...] Perhaps "infinitely hard" is the wrong criterion, but passing inode numbers lets a tracepoint client track changes to the same file, even though the file may be renamed/unlinked over time. - FChE -- 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