mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-22 01:47:47 +07:00
03cd45d2e2
The driver does not populate .reg_read callback for the non-active NVMem
because the file is supposed to be write-only. However, it turns out
NVMem subsystem does not yet support this and expects that the .reg_read
callback is provided. If user reads the binary attribute it triggers
NULL pointer dereference like this one:
BUG: kernel NULL pointer dereference, address: 0000000000000000
...
Call Trace:
bin_attr_nvmem_read+0x64/0x80
kernfs_fop_read+0xa7/0x180
vfs_read+0xbd/0x170
ksys_read+0x5a/0xd0
do_syscall_64+0x43/0x150
entry_SYSCALL_64_after_hwframe+0x44/0xa9
Fix this in the driver by providing .reg_read callback that always
returns an error.
Reported-by: Nicholas Johnson <nicholas.johnson-opensource@outlook.com.au>
Fixes:
|
||
---|---|---|
.. | ||
cap.c | ||
ctl.c | ||
ctl.h | ||
dma_port.c | ||
dma_port.h | ||
domain.c | ||
eeprom.c | ||
icm.c | ||
Kconfig | ||
lc.c | ||
Makefile | ||
nhi_ops.c | ||
nhi_regs.h | ||
nhi.c | ||
nhi.h | ||
path.c | ||
property.c | ||
switch.c | ||
tb_msgs.h | ||
tb_regs.h | ||
tb.c | ||
tb.h | ||
tmu.c | ||
tunnel.c | ||
tunnel.h | ||
usb4.c | ||
xdomain.c |