linux-kernel - Re: [PATCH] mm/z3fold.c: Reinitialize zhdr structs after migration

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] [day] [month] [year] [list]

Date:   Mon, 15 Jul 2019 14:21:23 -0700
From:   Henry Burns <henryburns@...gle.com>
To:     Vitaly Wool <vitalywool@...il.com>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        Vitaly Vul <vitaly.vul@...y.com>,
        Shakeel Butt <shakeelb@...gle.com>,
        Jonathan Adams <jwadams@...gle.com>,
        Linux MM <linux-mm@...ck.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm/z3fold.c: Reinitialize zhdr structs after migration

Sorry Vitaly, I had the wrong impression from your email that
INIT_LIST_HEAD() was being ensured directly in migrate and got
confused. (I thought you were saying it happened through the call to
do_compact_page() queued).

That being said, I don't see where in migrate new_zhdr->buddy is being
checked. We do check for new_zhdr.work with
 if (work_pending(&zhdr->work)) {
...
}

Is that what you were referring to?