mtd: Allocate bdi objects dynamically

The MTD backing dev info objects mtd_bdi was statically allocated.
So when MTD is built as a loadable module, this object fall in the
vmalloc address space.

The problem with that, is that the BDI APIs use wake_up_bit(), which calls
virt_to_page() to retrieve the memory zone of the page containing the
wait_queue to wake up, and virt_to_page() is not valid for vmalloc or
highmem addresses.

Fix this by allocating the BDI objects dynamically with kmalloc. The
objects now fall in the logical address space so that BDI APIs will
work in all cases (mtd builtin or module).

Signed-off-by: Steve Longerbeam <[email protected]>
Signed-off-by: Jim Baxter <[email protected]>
Signed-off-by: Sandeep Jain <[email protected]>
Reviewed-by: Richard Weinberger <[email protected]>
Reviewed-by: Marek Vasut <[email protected]>
Signed-off-by: Brian Norris <[email protected]>

0 files changed, 0 insertions, 0 deletions