Received-SPF: pass (google.com: domain of linux-kernel+bounces-157810-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
From: Luis Chamberlain <mcgrof@kernel.org>
To: akpm@linux-foundation.org,
	ziy@nvidia.com,
	linux-mm@kvack.org
Cc: fstests@vger.kernel.org,
	linux-xfs@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	willy@infradead.org,
	hare@suse.de,
	john.g.garry@oracle.com,
	p.raghav@samsung.com,
	da.gomez@samsung.com,
	mcgrof@kernel.org
Subject: [PATCH 0/2] mm/huge_memory: couple fixes and one cleanup
Date: Wed, 24 Apr 2024 15:54:47 -0700
Message-ID: <20240424225449.1498244-1-mcgrof@kernel.org>
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: Luis Chamberlain <mcgrof@infradead.org>

I've been stress testing large folio splits using the new debugfs interface
with a new fstests test [0], to make the debugfs interface more useful it helps
to do bounds checks on input parameters so this fixes two issues found while
doing automatic stress testing of the debugfs interface with found files.

Provided there are no issues I think this should go in for v6.9-rc6.

Also, *should* we strive to support splits for large folios to min order
with say MADV_NOHUGEPAGE ?

[0] https://lkml.kernel.org/r/20240424224649.1494092-1-mcgrof@kernel.org

Luis Chamberlain (2):
  mm/huge_memory: skip invalid debugfs file entry for folio split
  mm/huge_memory: cap max length on debugfs file entry folio split

 mm/huge_memory.c | 18 +++++++++++++++---
 1 file changed, 15 insertions(+), 3 deletions(-)

-- 
2.43.0