linux-kernel - Re: [PATCH] iov_iter: Declare new iterator direction symbols

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] [day] [month] [year] [list]

Date:   Fri, 4 Nov 2022 11:49:28 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     David Howells <dhowells@...hat.com>
Cc:     Al Viro <viro@...iv.linux.org.uk>,
        Christoph Hellwig <hch@...radead.org>, willy@...radead.org,
        dchinner@...hat.com, Steve French <smfrench@...il.com>,
        Shyam Prasad N <nspmangalore@...il.com>,
        Rohith Surabattula <rohiths.msft@...il.com>,
        Jeff Layton <jlayton@...nel.org>,
        Ira Weiny <ira.weiny@...el.com>, linux-cifs@...r.kernel.org,
        linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] iov_iter: Declare new iterator direction symbols

On Fri, Nov 4, 2022 at 10:47 AM David Howells <dhowells@...hat.com> wrote:
>
> If we're going to go with Al's changes to switch to using ITER_SOURCE and
> ITER_DEST instead of READ/WRITE, can we put just the new symbols into mainline
> now, even if we leave the rest for the next merge window?

No, I really don't want to have mixed-used stuff in the kernel.

Continue to use the old names until/if the conversion happens, at
which point it's the conversion code that does it.

No "one branch uses new names, another uses old names" mess.

               Linus