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: <ZDlP6EiwKDE35ZG7@infradead.org> Date: Fri, 14 Apr 2023 06:06:48 -0700 From: Christoph Hellwig <hch@...radead.org> To: Ritesh Harjani <ritesh.list@...il.com> Cc: Christoph Hellwig <hch@...radead.org>, linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org, Jan Kara <jack@...e.cz>, "Darrick J . Wong" <djwong@...nel.org>, Ojaswin Mujoo <ojaswin@...ux.ibm.com>, Disha Goel <disgoel@...ux.ibm.com> Subject: Re: [RFCv3 10/10] iomap: Add trace points for DIO path On Fri, Apr 14, 2023 at 01:26:38PM +0530, Ritesh Harjani wrote: > How about this below change? Does this look good to you? > It should cover all error types and both entry and exit. I don't think it is very useful. The complete tracepoint is the end of the I/O. Having a separate end one doesn't make sense. That's why I suggested a queued one for the asynchronous case.
Powered by blists - more mailing lists