linux-kernel - Re: [PATCH v2 00/53] fscache: Rewrite index API and management system

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: <1041557.1634931616@warthog.procyon.org.uk>
Date:   Fri, 22 Oct 2021 20:40:16 +0100
From:   David Howells <dhowells@...hat.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     dhowells@...hat.com, linux-cachefs@...hat.com,
        linux-afs@...ts.infradead.org,
        Marc Dionne <marc.dionne@...istor.com>,
        Eric Van Hensbergen <ericvh@...il.com>,
        "Matthew Wilcox (Oracle)" <willy@...radead.org>,
        Dave Wysochanski <dwysocha@...hat.com>,
        CIFS <linux-cifs@...r.kernel.org>,
        Dominique Martinet <asmadeus@...ewreck.org>,
        Steve French <sfrench@...ba.org>,
        Shyam Prasad N <nspmangalore@...il.com>,
        Jeff Layton <jlayton@...nel.org>,
        Anna Schumaker <anna.schumaker@...app.com>,
        linux-nfs@...r.kernel.org, Latchesar Ionkov <lucho@...kov.net>,
        v9fs-developer@...ts.sourceforge.net,
        Trond Myklebust <trond.myklebust@...merspace.com>,
        Trond Myklebust <trondmy@...merspace.com>,
        Jeff Layton <jlayton@...nel.com>,
        Alexander Viro <viro@...iv.linux.org.uk>,
        Omar Sandoval <osandov@...ndov.com>,
        ceph-devel@...r.kernel.org,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 00/53] fscache: Rewrite index API and management system

Linus Torvalds <torvalds@...ux-foundation.org> wrote:

> Honestly, I don't see the point of this when it ends up just being
> dead code basically immediately.
> 
> You don't actually support picking one or the other at build time,
> just a hard switch-over.
> 
> That makes the old fscache driver useless. You can't say "use the old
> one because I don't trust the new". You just have a legacy
> implementation with no users.

What's the best way to do this?  Is it fine to disable caching in all the
network filesystems and then directly remove the fscache and cachefiles
drivers and replace them?  It won't stop the network filesystems actually
working - it'll just mean that they don't do any caching until converted and
have caching reenabled.

David