On May 27, 2025 / 12:34, Bart Van Assche wrote: > On 5/26/25 1:25 AM, Shinichiro Kawasaki wrote: > > On May 23, 2025 / 09:49, Bart Van Assche wrote: > > > + _init_null_blk nr_devices=0 queue_mode=2 > > > > This line can be removed by renameing the null_blk devices as follows: > > > > nullb0 -> nullb1 > > nullb1 -> nullb2 > > > > nullb0 is not recommended since it can not be reconfigured when the > > null_blk driver is built-in. > Isn't _remove_null_blk_devices() supposed to remove nullb0 no matter > whether null_blk is a kernel module or built-in to the kernel? No. When null_blk is built-in, it creates /dev/nullb0, but does not create the nullb0 directory under kernel config directory path. > And if > the null_blk driver has been built as a kernel module, how is it > supposed to be loaded without calling _init_null_blk()? _configure_null_blk() calls modprobe to load the null_blk module.
