linux-kernel - Re: [PATCH v2] mm,hwpoison: return -EBUSY when page already poisoned

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: <20210313015531.1737679-1-juew@google.com>
Date:   Fri, 12 Mar 2021 17:55:31 -0800
From:   Jue Wang <juew@...gle.com>
To:     tony.luck@...el.com
Cc:     akpm@...ux-foundation.org, bp@...en8.de, david@...hat.com,
        hpa@...or.com, linux-edac@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-mm@...ck.org, mingo@...hat.com,
        naoya.horiguchi@....com, osalvador@...e.de, tglx@...utronix.de,
        x86@...nel.org, yangfeng1@...gsoft.com, yaoaili@...gsoft.com
Subject: Re: [PATCH v2] mm,hwpoison: return -EBUSY when page already poisoned

I believe the mutex type patch has its own value in protecting 
memory_failure from other inherent races, e.g., races around 
split_huge_page where concurrent MCE happens to different 4k pages 
under the same THP.[1] This realistically can happen given the physical
locality clustering effect of memory errors.

Thanks,
-Jue

[1] The split fails due to a page reference taken by other concurrent 
calling into memory_failure on the same THP.