linux-kernel - Re: [PATCH v13 00/72] Convert page cache to XArray

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]

Date:   Tue, 12 Jun 2018 12:46:19 -0700
From:   Matthew Wilcox <willy@...radead.org>
To:     Ross Zwisler <ross.zwisler@...ux.intel.com>, dsterba@...e.cz,
        linux-mm@...ck.org, linux-fsdevel@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Matthew Wilcox <mawilcox@...rosoft.com>,
        Jan Kara <jack@...e.cz>, Jeff Layton <jlayton@...hat.com>,
        Lukas Czerner <lczerner@...hat.com>,
        Christoph Hellwig <hch@....de>,
        Goldwyn Rodrigues <rgoldwyn@...e.com>,
        Nicholas Piggin <npiggin@...il.com>,
        Ryusuke Konishi <konishi.ryusuke@....ntt.co.jp>,
        linux-nilfs@...r.kernel.org, Jaegeuk Kim <jaegeuk@...nel.org>,
        Chao Yu <yuchao0@...wei.com>,
        linux-f2fs-devel@...ts.sourceforge.net
Subject: Re: [PATCH v13 00/72] Convert page cache to XArray

On Tue, Jun 12, 2018 at 01:37:41PM -0600, Ross Zwisler wrote:
> On Tue, Jun 12, 2018 at 04:31:22AM -0700, Matthew Wilcox wrote:
> > On Tue, Jun 12, 2018 at 12:40:41PM +0200, David Sterba wrote:
> > > [ 9875.174796] kernel BUG at fs/inode.c:513!
> > 
> > What the ...
> > 
> > Somehow the fix for that got dropped.  I spent most of last week chasing
> > that problem!  This is the correct code:
> > 
> > http://git.infradead.org/users/willy/linux-dax.git/commitdiff/01177bb06761539af8a6c872416109e2c8b64559
> > 
> > I'll check over the patchset and see if anything else got dropped!
> 
> Can you please repost when you have this sorted?
> 
> I think the commit you've pointed to is in your xarray-20180601 branch, but I
> see two more recent xarray branches in your tree (xarray-20180608 and
> xarray-20180612).
> 
> Basically, I don't know what is stable and what's not, and what I should be
> reviewing/testing.

Yup, I shall.  The xarray-20180612 is the most recent thing I've
published, but I'm still going over the 0601 patchset looking for other
little pieces I may have dropped.  I've found a couple, and I'm updating
the 0612 branch each time I find another one.

If you want to start looking at the DAX patches on the 0612 branch,
that wouldn't be a waste of your time.  Neither would testing; I don't
think I dropped anything from the DAX patches.