Patch "dm-crypt: start allocating with MAX_ORDER" has been added to the 6.6-stable tree

[Sasha Levin <sashal@kernel.org>]

This is a note to let you know that I've just added the patch titled

    dm-crypt: start allocating with MAX_ORDER

to the 6.6-stable tree which can be found at:
    http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     dm-crypt-start-allocating-with-max_order.patch
and it can be found in the queue-6.6 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.



commit 622358e7f48feee3351300a2af4163f1258fcc7b
Author: Mikulas Patocka <mpatocka@redhat.com>
Date:   Fri Nov 17 18:38:33 2023 +0100

    dm-crypt: start allocating with MAX_ORDER
    
    [ Upstream commit 13648e04a9b831b3dfa5cf3887dfa6cf8fe5fe69 ]
    
    Commit 23baf831a32c ("mm, treewide: redefine MAX_ORDER sanely")
    changed the meaning of MAX_ORDER from exclusive to inclusive. So, we
    can allocate compound pages with up to 1 << MAX_ORDER pages.
    
    Reflect this change in dm-crypt and start trying to allocate compound
    pages with MAX_ORDER.
    
    Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
    Signed-off-by: Mike Snitzer <snitzer@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>

diff --git a/drivers/md/dm-crypt.c b/drivers/md/dm-crypt.c
index cef9353370b20..17ffbf7fbe73e 100644
--- a/drivers/md/dm-crypt.c
+++ b/drivers/md/dm-crypt.c
@@ -1679,7 +1679,7 @@ static struct bio *crypt_alloc_buffer(struct dm_crypt_io *io, unsigned int size)
 	unsigned int nr_iovecs = (size + PAGE_SIZE - 1) >> PAGE_SHIFT;
 	gfp_t gfp_mask = GFP_NOWAIT | __GFP_HIGHMEM;
 	unsigned int remaining_size;
-	unsigned int order = MAX_ORDER - 1;
+	unsigned int order = MAX_ORDER;
 
 retry:
 	if (unlikely(gfp_mask & __GFP_DIRECT_RECLAIM))