linux-kernel - Re: [GIT PULL] XArray for 4.20

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: <CAHk-=whquhQQY38WRKYsi-_a2vD=_22EPEnfVj4+APEjZPAkMw@mail.gmail.com>
Date:   Sun, 28 Oct 2018 11:50:19 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     willy@...radead.org
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] XArray for 4.20

On Tue, Oct 23, 2018 at 1:08 PM Matthew Wilcox <willy@...radead.org> wrote:
<
> Please consider pulling the XArray patch set.

Pulled.

I took the more recent version of yours, because by the time I
actually had time to review this thing for pulling, even the recent
version had been in linux-next for a week.

Of course, I don't think linux-next has been updated, so it's all
moot, but the point is that I didn't get the feeling that it was all
some very recent code.

I do like how the conversions look, with the code in some cases
notably simpler. And it looks like at least one of the conflicts
(fs/dax.c) was due to a bug-fix to the old code where your simpler
xarray replacement didn't have the problem.

NOTE! I did get some conflicts with other stuff, and while the
conflict resolution all looked pretty straightforward, this does want
looking at.

Particularly the mm/workingset.c code.

It's still undergoing my build tests to verify my merge, but that
should be completed soon. I'll do a basic boot test too due to the
core nature of these changes, but assuming it all passes I'll push
this out within the next 30 minutes and would appreciate people giving
it a second look for verification.

Thanks,

                      Linus