Re: [Crash-utility] linux-next broke module_init()
Hi Alex,
On 2023/02/15 21:26, Alexander Egorenkov wrote:
Hi,
it seems this linux-next patch
https://lore.kernel.org/all/20230207002802.2514802-1-song@kernel.org/
broke module_init().
Thank you for the early notice!
ugh... module memory regions now scattered?
machdep_init(POST_VM);
//module_init();
help_init();
crash> enum mod_mem_type
enum mod_mem_type {
MOD_TEXT = 0
MOD_DATA = 1
MOD_RODATA = 2
MOD_RO_AFTER_INIT = 3
MOD_INIT_TEXT = 4
MOD_INIT_DATA = 5
MOD_INIT_RODATA = 6
MOD_MEM_NUM_TYPES = 7
MOD_INVALID = -1
};
crash> list -H modules -o module.list -s module.name,mem -x | grep -e base -e name -e
size
name = "rfkill\000\000\000\000\000\000\000...
base = 0xffffffffc09df000, MOD_TEXT
size = 0x3000,
base = 0xffffffffc09ee000, MOD_DATA
size = 0x4000,
base = 0xffffffffc09e3000, MOD_RODATA
size = 0x3000,
base = 0x0, ...
size = 0x0,
base = 0x0,
size = 0x0,
base = 0x0,
size = 0x0,
base = 0x0,
size = 0x0,
name = "sunrpc\000\000\000\000\000\000\000...
base = 0xffffffffc0a12000,
size = 0x3d000,
base = 0xffffffffc0a96000,
size = 0x58000,
base = 0xffffffffc0bbe000,
size = 0x2e000,
base = 0xffffffffc09dd000,
size = 0x1000,
base = 0x0,
size = 0x0,
base = 0x0,
size = 0x0,
base = 0x0,
size = 0x0,
...
Not sure what is the correct way to approach to fix this.
I would appreciate any hints how to fix this.
I've not looked into it enough, but feels like maybe we have to
track the scattered regions...
Thanks,
Kazu