| 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: Fri, 20 Nov 2009 08:45:37 -0800 From: Arjan van de Ven <arjan@...radead.org> To: Jamie Lokier <jamie@...reable.org> Cc: Christoph Hellwig <hch@...radead.org>, Ingo Molnar <mingo@...e.hu>, "Kok, Auke" <auke-jan.h.kok@...el.com>, "Frank Ch. Eigler" <fche@...hat.com>, Jeff Garzik <jeff@...zik.org>, "Wu, Fengguang" <fengguang.wu@...el.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>, Al Viro <viro@...IV.linux.org.uk>, Frederic Weisbecker <fweisbec@...il.com> Subject: Re: [PATCH] vfs: Add a trace point in the mark_inode_dirty function On Fri, 20 Nov 2009 16:05:26 +0000 Jamie Lokier <jamie@...reable.org> wrote: > Arjan van de Ven wrote: > > in my case it's not about finding the file, but finding the place in > > the application that is doing the writing. The last pathname > > component is more than enough for this.... > > So what you really need is the source file and line number in your > application where it does the writing :-) while you present this as a joke.... perf can more or less do this using the backtrace infrastructure ... -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org -- 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