orangefs: Fix the size of a memory allocation in orangefs_bufmap_alloc()
authorChristophe JAILLET <christophe.jaillet@wanadoo.fr>
Mon, 27 Dec 2021 18:09:18 +0000 (19:09 +0100)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 20 Jan 2022 08:13:13 +0000 (09:13 +0100)
commitb07490067dbcce915686257b0821da44d744b682
treebe138e117a0ab0a179560812301e0d45b10c4b44
parentce258c74f8d95e81ce65f53775fcdcbc8ca090da
orangefs: Fix the size of a memory allocation in orangefs_bufmap_alloc()

commit 40a74870b2d1d3d44e13b3b73c6571dd34f5614d upstream.

'buffer_index_array' really looks like a bitmap. So it should be allocated
as such.
When kzalloc is called, a number of bytes is expected, but a number of
longs is passed instead.

In get(), if not enough memory is allocated, un-allocated memory may be
read or written.

So use bitmap_zalloc() to safely allocate the correct memory size and
avoid un-expected behavior.

While at it, change the corresponding kfree() into bitmap_free() to keep
the semantic.

Fixes: ea2c9c9f6574 ("orangefs: bufmap rewrite")
Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Signed-off-by: Mike Marshall <hubcap@omnibond.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/orangefs/orangefs-bufmap.c