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, 21 Apr 2010 23:27:27 +0200 From: Jens Axboe <jens.axboe@...cle.com> To: "Darrick J. Wong" <djwong@...ibm.com> Cc: linux-kernel <linux-kernel@...r.kernel.org>, linux-ext4 <linux-ext4@...r.kernel.org> Subject: Re: [PATCH] block: Add a trace point whenever a barrier IO request is sent On Wed, Apr 21 2010, Darrick J. Wong wrote: > Simple debugging patch used to watch for barrier requests. I've been using > this to watch ext4's barrier=1 behavior. But barriers are already being logged, if you watch blkparse data, it'll be RB or WB events. So I don't see what this addition provides that we don't already have? -- Jens Axboe -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists