On 17/03/2023 10:26, Dan Williams wrote:
> lizhij...@fujitsu.com wrote:
>>
>>
>> On 16/03/2023 23:54, Dan Williams wrote:
>>> Li Zhijian wrote:
nvdimm_bus_register() could be called from other modules, such as nfit,
but it can only be called after the nvdimm_bus_type is registered.
As is mentioned[1] before, the generic/388 will randomly fail with dmesg
warning. This case uses fsstress with a lot of random operations. It is hard
to reproduce. Finally I found a 100% reproduce condition, which is setting
the seed to 1677104360. So I changed the generic/388 code: removed
lizhij...@fujitsu.com wrote:
>
>
> On 16/03/2023 23:54, Dan Williams wrote:
> > Li Zhijian wrote:
> >> nvdimm_bus_register() could be called from other modules, such as nfit,
> >> but it can only be called after the nvdimm_bus_type is registered.
> >>
> >> BUG: kernel NULL pointer dereference,
On 16/03/2023 23:54, Dan Williams wrote:
> Li Zhijian wrote:
>> nvdimm_bus_register() could be called from other modules, such as nfit,
>> but it can only be called after the nvdimm_bus_type is registered.
>>
>> BUG: kernel NULL pointer dereference, address: 0098
>> #PF:
Li Zhijian wrote:
> nvdimm_bus_register() could be called from other modules, such as nfit,
> but it can only be called after the nvdimm_bus_type is registered.
>
> BUG: kernel NULL pointer dereference, address: 0098
> #PF: supervisor read access in kernel mode
> #PF:
nvdimm_bus_register() could be called from other modules, such as nfit,
but it can only be called after the nvdimm_bus_type is registered.
BUG: kernel NULL pointer dereference, address: 0098
#PF: supervisor read access in kernel mode
#PF: error_code(0x) - not-present page
PGD
6 matches
Mail list logo