dm-crypt: start allocating with MAX_ORDER
authorMikulas Patocka <mpatocka@redhat.com>
Fri, 17 Nov 2023 17:38:33 +0000 (18:38 +0100)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Wed, 13 Dec 2023 17:45:01 +0000 (18:45 +0100)
commitdfa1898cef4c33fefb402d3aec1cca8df146e34c
tree8370a3c3d63025f48b1be45e51d0a919de4e6866
parent915864d18641ff263efdef887d699b9103ee0878
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>
drivers/md/dm-crypt.c