linux-kernel - Re: [PATCH 06/14] fs: remove the call_{read,write}

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200528185643.GL23230@ZenIV.linux.org.uk>
Date:   Thu, 28 May 2020 19:56:43 +0100
From:   Al Viro <viro@...iv.linux.org.uk>
To:     Christoph Hellwig <hch@....de>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Ian Kent <raven@...maw.net>,
        David Howells <dhowells@...hat.com>,
        linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
        linux-security-module@...r.kernel.org,
        netfilter-devel@...r.kernel.org
Subject: Re: [PATCH 06/14] fs: remove the call_{read,write}_iter functions

On Thu, May 28, 2020 at 07:40:35AM +0200, Christoph Hellwig wrote:
> Just open coding the methods calls is a lot easier to follow.

Not sure about this one, TBH - it's harder to grep that way, since
you get all the initializers for read_iter/write_iter thrown into
the mix.  Sure, you can do something like '\->[ 	]*read_iter\>',
but it's a PITA.