linux-kernel - Re: [PATCH 1/2] mm/huge_memory: check new folio order when split a folio

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: Thu, 7 Mar 2024 12:02:24 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Zi Yan <ziy@...dia.com>
Cc: Zi Yan <zi.yan@...t.com>, linux-mm@...ck.org, Dan Carpenter
 <dan.carpenter@...aro.org>, "Pankaj Raghav (Samsung)"
 <kernel@...kajraghav.com>, "Matthew Wilcox (Oracle)" <willy@...radead.org>,
 David Hildenbrand <david@...hat.com>, Yang Shi <shy828301@...il.com>, Yu
 Zhao <yuzhao@...gle.com>, "Kirill A . Shutemov"
 <kirill.shutemov@...ux.intel.com>, Ryan Roberts <ryan.roberts@....com>,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] mm/huge_memory: check new folio order when split a
 folio

On Thu,  7 Mar 2024 13:18:53 -0500 Zi Yan <zi.yan@...t.com> wrote:

> From: Zi Yan <ziy@...dia.com>
> 
> A folio can only be split into lower orders. Check new_order to make sure
> it is smaller than input folio order.

It isn't clear what's being fixed here.  Presumably something is
passing in such folios, but what and where and why and what are the
effects?

Might it be that these folios are being caused by the debugfs
interface?  Or something else?

So I'll add it, but I do think more information and context would
improve the patch, please.  Suitable Reported-by:, Closes: and Link:
tags, perhaps.