linux-kernel - Re: [MAINTAINER SUMMIT] Folios as a potential Kernel/Maintainers Summit topic?

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: <YUJcN/dqa8f4R9w0@mit.edu>
Date:   Wed, 15 Sep 2021 16:48:55 -0400
From:   "Theodore Ts'o" <tytso@....edu>
To:     James Bottomley <James.Bottomley@...senpartnership.com>
Cc:     Chris Mason <clm@...com>, Johannes Weiner <hannes@...xchg.org>,
        Kent Overstreet <kent.overstreet@...il.com>,
        Matthew Wilcox <willy@...radead.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        "linux-mm@...ck.org" <linux-mm@...ck.org>,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        "Darrick J. Wong" <djwong@...nel.org>,
        Christoph Hellwig <hch@...radead.org>,
        David Howells <dhowells@...hat.com>,
        "ksummit@...ts.linux.dev" <ksummit@...ts.linux.dev>
Subject: Re: [MAINTAINER SUMMIT] Folios as a potential Kernel/Maintainers
 Summit topic?

On Wed, Sep 15, 2021 at 03:15:13PM -0400, James Bottomley wrote:
> 
> My reading of the email threads is that they're iterating to an actual
> conclusion (I admit, I'm surprised) ... or at least the disagreements
> are getting less.  Since the merge window closed this is now a 5.16
> thing, so there's no huge urgency to getting it resolved next week.

My read was that it was more that people were just getting exhausted,
and not necessarily that folks were converging.  (Also, Willy is
currently on vacation.)

I'm happy to be wrong, bu the patches haven't changed since the merge
window opened, and it's not clear what *needs* to change before it can
be accepted at the next merge window.

> Well, the current one seems to be working (admittedly eventually, so
> achieving faster resolution next time might be good) ... but I'm sure
> you could propose alternatives ... especially in the time to resolution
> department.

Given how long it took for DAX to converge (years and years and years
and *multiple* LSF/MM's), I'm not as optimistic that Folios is
converge and is about to be merged at the next merge window.  But
again, I'm happy to be proven wrong.

						- Ted