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]
Date:   Mon, 15 Feb 2021 00:22:57 +0000
From:   David Howells <>
To:     Linus Torvalds <>
Cc:, Matthew Wilcox <>,
        Jeff Layton <>,
        David Wysochanski <>,
        Anna Schumaker <>,
        Trond Myklebust <>,
        Steve French <>,
        Dominique Martinet <>,
        Alexander Viro <>,,,, CIFS <>,
        linux-fsdevel <>,
        "open list:NFS, SUNRPC, AND..." <>,,
        Linux Kernel Mailing List <>
Subject: Re: [GIT PULL] fscache: I/O API modernisation and netfs helper library

Linus Torvalds <> wrote:

> But no, it's not a replacement for actual code review after the fact.
> If you think email has too long latency for review, and can't use
> public mailing lists and cc the people who are maintainers, then I
> simply don't want your patches.

I think we were talking at cross-purposes by the term "development" here.  I
was referring to the discussion of how the implementation should be done and
working closely with colleagues - both inside and outside Red Hat - to get
things working, not specifically the public review side of things.  It's just
that I don't have a complete record of the how-to-implement-it, the
how-to-get-various-bits-working-together and the why-is-it-not-working?

Anyway, I have posted my fscache modernisation patches multiple times for
public review, I have tried to involve the wider community in aspects of the
development on public mailing lists and I have been including the maintainers
in to/cc.

I've posted the more full patchset for public review a number of times:

4th May 2020:

13th Jul (split into three subsets):

20th Nov:

I then cut it down and posted that publically a couple of times:

20th Jan:

25th Jan:

I let you know what was coming here:

to try and find out whether you were going to have any objections to the
design in advance, rather than at the last minute.

I've apprised people of what I was up to:

Asked for consultation on parts of what I wanted to do:

Asked someone who is actually using fscache in production to test the rewrite:

I've posted partial patches to try and help 9p and cifs along:

(Jeff has been handling Ceph and Dave NFS).

Proposed conference topics related to this:

though the lockdown put paid to that:-(

Willy has discussed it too:


Powered by blists - more mailing lists