Hi,
After today's pull on linux-block/for-next test QEMU is not able to
boot, any information about how to solve this will be helpful as
it is blocking blktest testing, here is dmsg :-
[ 1.304698] ata1.00: Read log 0x00 page 0x00 failed, Emask 0x1
[ 1.305587] ata1.01: Read log 0x00 page 0x00 failed, Emask 0x1
[ 1.455959] systemd[1]: Cannot be run in a chroot() environment.
[ 1.456743] systemd[1]: Freezing execution.
HEAD:-
# git log -2
commit 5774f2f04654804f8e0a40cfe8ff3f8ce3c0b6c9 (HEAD -> for-next,
origin/for-next)
Merge: 7e0469db34b8 2ff4ec783f4c
Author: Jens Axboe <axboe@xxxxxxxxx>
Date: Tue Feb 22 13:00:39 2022 -0700
Merge branch 'for-5.18/drivers' into for-next
* for-5.18/drivers:
null_blk: null_alloc_page() cleanup
null_blk: remove hardcoded null_alloc_page() param
commit 2ff4ec783f4c635289384398d14b241f21bce269 (origin/for-5.18/drivers)
Author: Chaitanya Kulkarni <kch@xxxxxxxxxx>
Date: Tue Feb 22 07:28:52 2022 -0800
null_blk: null_alloc_page() cleanup
Remove goto labels and use direct returns as error unwinding code only
needs to free t_page variable if we alloc_pages() call fails as having
two labels for one kfree() can be avoided easily.
Signed-off-by: Chaitanya Kulkarni <kch@xxxxxxxxxx>
Reviewed-by: Christoph Hellwig <hch@xxxxxx>
Link: https://lore.kernel.org/r/20220222152852.26043-3-kch@xxxxxxxxxx
Signed-off-by: Jens Axboe <axboe@xxxxxxxxx>
-ck
