On Tue, Mar 19, 2024 at 06:45:14AM +0000, Shinichiro Kawasaki wrote: > #2: nvme/041,044 (fc transport) > > With the trtype=fc configuration, nvme/041 and 044 fail with similar > error messages: > > nvme/041 (Create authenticated connections) [failed] > runtime 2.677s ... 4.823s > --- tests/nvme/041.out 2023-11-29 12:57:17.206898664 +0900 > +++ /home/shin/Blktests/blktests/results/nodev/nvme/041.out.bad 2024-03-19 14:50:56.399101323 +0900 > @@ -2,5 +2,5 @@ > Test unauthenticated connection (should fail) > disconnected 0 controller(s) > Test authenticated connection > -disconnected 1 controller(s) > +disconnected 0 controller(s) > Test complete > nvme/044 (Test bi-directional authentication) [failed] > runtime 4.740s ... 7.482s > --- tests/nvme/044.out 2023-11-29 12:57:17.212898647 +0900 > +++ /home/shin/Blktests/blktests/results/nodev/nvme/044.out.bad 2024-03-19 14:51:08.062067741 +0900 > @@ -4,7 +4,7 @@ > Test invalid ctrl authentication (should fail) > disconnected 0 controller(s) > Test valid ctrl authentication > -disconnected 1 controller(s) > +disconnected 0 controller(s) > Test invalid ctrl key (should fail) > disconnected 0 controller(s) > ... > (Run 'diff -u tests/nvme/044.out /home/shin/Blktests/blktests/results/nodev/nvme/044.out.bad' to see the entire diff) FTR, https://lore.kernel.org/linux-nvme/20240221132404.6311-1-dwagner@suse.de/ Hannes has told me he has another idea how we could solve this problem and he wants to post some patches.
Hi all, I ran the latest blktests (git hash: 607513e64e48) with the v6.8 kernel, and I observed three failures. I also checked CKI project blktests runs with the v6.8 kernel, and found two failures. In total, five failure symptoms are observed as listed below. Compared with the v6.8-rc1 kernel [1], nvme test group has greatly improved for fc transport (Thanks go to Daniel). Now test runs do not hang. A few test cases still fail, but it is a great improvement :) [1] https://lore.kernel.org/linux-block/44i4y3fyqcz6k2pmum6toqylc2lvveb7x37ngskzfof52hoi2r@vxdxdnmggbj5/ List of failures ================ #1: block/011 #2: nvme/041,044 (fc transport) #3: srp/002, 011 (rdma_rxe driver) #4: nbd/002 (CKI failure) #5: zbd/010 (CKI failure) Failure description =================== #1: block/011 The test case fails with NVME devices due to lockdep WARNING "possible circular locking dependency detected". Reported in Sep/2022 [2]. In LSF 2023, it was noted that this failure should be fixed. A RFC fix patch was posted recently [3]. It still needs more discussion to be fixed. [2] https://lore.kernel.org/linux-block/20220930001943.zdbvolc3gkekfmcv@shindev/ [3] https://lore.kernel.org/linux-nvme/20231213051704.783490-1-shinichiro.kawasaki@wdc.com/ #2: nvme/041,044 (fc transport) With the trtype=fc configuration, nvme/041 and 044 fail with similar error messages: nvme/041 (Create authenticated connections) [failed] runtime 2.677s ... 4.823s --- tests/nvme/041.out 2023-11-29 12:57:17.206898664 +0900 +++ /home/shin/Blktests/blktests/results/nodev/nvme/041.out.bad 2024-03-19 14:50:56.399101323 +0900 @@ -2,5 +2,5 @@ Test unauthenticated connection (should fail) disconnected 0 controller(s) Test authenticated connection -disconnected 1 controller(s) +disconnected 0 controller(s) Test complete nvme/044 (Test bi-directional authentication) [failed] runtime 4.740s ... 7.482s --- tests/nvme/044.out 2023-11-29 12:57:17.212898647 +0900 +++ /home/shin/Blktests/blktests/results/nodev/nvme/044.out.bad 2024-03-19 14:51:08.062067741 +0900 @@ -4,7 +4,7 @@ Test invalid ctrl authentication (should fail) disconnected 0 controller(s) Test valid ctrl authentication -disconnected 1 controller(s) +disconnected 0 controller(s) Test invalid ctrl key (should fail) disconnected 0 controller(s) ... (Run 'diff -u tests/nvme/044.out /home/shin/Blktests/blktests/results/nodev/nvme/044.out.bad' to see the entire diff) #3: srp/002, 011 (rdma_rxe driver) Test process hang is observed occasionally. Reported to the relevant mailing lists in Aug/2023 [4]. Blktests was modified to change the default driver from rdma_rxe to siw to avoid impacts on blktests users. The root cause is not yet understood. [4] https://lore.kernel.org/linux-rdma/18a3ae8c-145b-4c7f-a8f5-67840feeb98c@acm.org/T/#mee9882c2cfd0cfff33caa04e75418576f4c7a789 #4: nbd/002 (CKI failure) CKI reported the failure [5]. I confirmed the test case fail occasionally on my test machine. I think blktests script can be improved to avoid the failure. I plan to post a fix candidate patch. nbd/002 (tests on partition handling for an nbd device) [failed] runtime ... 0.414s --- tests/nbd/002.out 2024-02-19 19:25:07.453721466 +0900 +++ /home/shin/kts/kernel-test-suite/sets/blktests/log/runlog/nodev/nbd/002.out.bad 2024-03-19 14:53:56.320218177 +0900 @@ -1,4 +1,4 @@ Running nbd/002 Testing IOCTL path Testing the netlink path -Test complete +Didn't have partition on the netlink path [5] https://datawarehouse.cki-project.org/kcidb/tests/11634679 #5: zbd/010 (CKI failure) CKI observed the failure [6], and Yi Zhang reported it to relevant mailing lists [7]. Though the WARN was observed with the test case zbd/010 for zoned block devices, it can be recreated with non-zoned regular block devices, when f2fs is set up with multiple block devices. A fix in F2FS is expected. [6] https://datawarehouse.cki-project.org/issue/2508 [7] https://lore.kernel.org/linux-f2fs-devel/CAHj4cs-kfojYC9i0G73PRkYzcxCTex=-vugRFeP40g_URGvnfQ@mail.gmail.com/
On 3/17/24 20:07, Li zeming wrote:
> ret is assigned first, so it does not need to initialize the assignment.
>
> Signed-off-by: Li zeming <zeming@nfschina.com>
> ---
> block/blk-pm.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/block/blk-pm.c b/block/blk-pm.c
> index 42e8420747153..c76d5a3169417 100644
> --- a/block/blk-pm.c
> +++ b/block/blk-pm.c
> @@ -58,10 +58,10 @@ EXPORT_SYMBOL(blk_pm_runtime_init);
> */
> int blk_pre_runtime_suspend(struct request_queue *q)
> {
> - int ret = 0;
> + int ret;
>
> if (!q->dev)
> - return ret;
> + return 0;
>
> WARN_ON_ONCE(q->rpm_status != RPM_ACTIVE);
>
I don't see why we need this patch, existing code is fine ...
-ck
On 3/17/24 19:55, Li zeming wrote:
> ret is assigned first, so it does not need to initialize the assignment.
>
> Signed-off-by: Li zeming <zeming@nfschina.com>
> ---
>
Looks good.
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
-ck
On Mon, Mar 18, 2024 at 5:38 PM Changhui Zhong <czhong@redhat.com> wrote: > > Hello, > > found a kernel panic issue on blktests nbd/003, please help check > > repo:https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > branch: master > commit HEAD:c442a42363b2ce5c3eb2b0ff1e052ee956f0a29f > > [ 2519.746767] run blktests nbd/003 at 2024-03-15 18:22:55 looks the same issue as https://lore.kernel.org/linux-block/CAHj4cs--N4tDj6ZKACCGEHcBYG9NqEvM-Kiu6UEq0WejypD9TQ@mail.gmail.com/T/#m50404b005619119f0ffe574db32a231d4e9577fb
Hi, 在 2024/03/19 10:13, Matthew Sakai 写道: > > On 3/18/24 21:43, Yu Kuai wrote: >> Hi, >> >> 在 2024/03/19 9:18, Yu Kuai 写道: >>> Hi, >>> >>> 在 2024/03/18 17:39, Christian Brauner 写道: >>>> On Sat, Mar 16, 2024 at 10:49:33AM +0800, Yu Kuai wrote: >>>>> Hi, Christian >>>>> >>>>> 在 2024/03/15 21:54, Christian Brauner 写道: >>>>>> On Fri, Mar 15, 2024 at 08:08:49PM +0800, Yu Kuai wrote: >>>>>>> Hi, Christian >>>>>>> Hi, Christoph >>>>>>> Hi, Jan >>>>>>> >>>>>>> Perhaps now is a good time to send a formal version of this set. >>>>>>> However, I'm not sure yet what branch should I rebase and send >>>>>>> this set. >>>>>>> Should I send to the vfs tree? >>>>>> >>>>>> Nearly all of it is in fs/ so I'd say yes. >>>>>> . >>>>> >>>>> I see that you just create a new branch vfs.fixes, perhaps can I >>>>> rebase >>>>> this set against this branch? >>>> >>>> Please base it on vfs.super. I'll rebase it to v6.9-rc1 on Sunday. >>> >>> Okay, I just see that vfs.super doesn't contain commit >>> 1cdeac6da33f("btrfs: pass btrfs_device to btrfs_scratch_superblocks()"), >>> and you might need to fix the conflict at some point. >> >> And there is another problem, dm-vdo doesn't exist in vfs.super yet. Do >> you still want me to rebase here? >> > > The dm-vdo changes don't appear to rely on earlier patches in the > series, so I think dm-vdo could incorporate the dm-vdo patch > independently from the rest of the series, if that would be helpful. (I > don't want to confuse things too much.) In that case it would go through > the dm tree with the rest of dm-vdo. We want to remove the 'bd_inode' field in this set. And if we want to go through dm tree for dm-vdo changes, we must keep the field for now. I don't have preference, Christian will make the decision. 😉 Thanks, Kuai > > Matt > > . >
On 2024/3/18 13:47, Shinichiro Kawasaki via Linux-f2fs-devel wrote: > I confirmed that the trigger commit is dbf8e63f48af as Yi reported. I took a > look in the commit, but it looks fine to me. So I thought the cause is not > in the commit diff. > > I found the WARN is printed when the f2fs is set up with multiple devices, > and read requests are mapped to the very first block of the second device in the > direct read path. In this case, f2fs_map_blocks() and f2fs_map_blocks_cached() > modify map->m_pblk as the physical block address from each block device. It > becomes zero when it is mapped to the first block of the device. However, > f2fs_iomap_begin() assumes that map->m_pblk is the physical block address of the > whole f2fs, across the all block devices. It compares map->m_pblk against > NULL_ADDR == 0, then go into the unexpected branch and sets the invalid > iomap->length. The WARN catches the invalid iomap->length. > > This WARN is printed even for non-zoned block devices, by following steps. > > - Create two (non-zoned) null_blk devices memory backed with 128MB size each: > nullb0 and nullb1. > # mkfs.f2fs /dev/nullb0 -c /dev/nullb1 > # mount -t f2fs /dev/nullb0 "${mount_dir}" > # dd if=/dev/zero of="${mount_dir}/test.dat" bs=1M count=192 > # dd if="${mount_dir}/test.dat" of=/dev/null bs=1M count=192 iflag=direct > > I created a fix candidate patch [1]. It modifies f2fs_iomap_begin() to handle > map->m_pblk as the physical block address from each device start, not the > address of whole f2fs. I confirmed it avoids the WARN. > > But I'm not so sure if the fix is good enough. map->m_pblk has dual meanings. > Sometimes it holds the physical block address of each device, and sometimes > the address of the whole f2fs. I'm not sure what is the condition for > map->m_pblk to have which meaning. I guess F2FS_GET_BLOCK_DIO flag is the > condition, but f2fs_map_blocks_cached() does not ensure it. > > Also, I noticed that map->m_pblk is referred to in other functions below, and > not sure if they need the similar change as I did for f2fs_iomap_begin(). > > f2fs_fiemap() > f2fs_read_single_page() > f2fs_bmap() > check_swap_activate() > > I would like to hear advices from f2fs experts for the fix. > > > [1] > > diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c > index 26e317696b33..5232223a69e5 100644 > --- a/fs/f2fs/data.c > +++ b/fs/f2fs/data.c > @@ -1569,6 +1569,7 @@ static bool f2fs_map_blocks_cached(struct inode *inode, > int bidx = f2fs_target_device_index(sbi, map->m_pblk); > struct f2fs_dev_info *dev = &sbi->devs[bidx]; > > + map->m_multidev_dio = true; > map->m_bdev = dev->bdev; > map->m_pblk -= dev->start_blk; > map->m_len = min(map->m_len, dev->end_blk + 1 - map->m_pblk); > @@ -4211,9 +4212,11 @@ static int f2fs_iomap_begin(struct inode *inode, loff_t offset, loff_t length, > unsigned int flags, struct iomap *iomap, > struct iomap *srcmap) > { > + struct f2fs_sb_info *sbi = F2FS_I_SB(inode); > struct f2fs_map_blocks map = {}; > pgoff_t next_pgofs = 0; > - int err; > + block_t pblk; > + int err, i; > > map.m_lblk = bytes_to_blks(inode, offset); > map.m_len = bytes_to_blks(inode, offset + length - 1) - map.m_lblk + 1; > @@ -4239,12 +4242,17 @@ static int f2fs_iomap_begin(struct inode *inode, loff_t offset, loff_t length, > * We should never see delalloc or compressed extents here based on > * prior flushing and checks. > */ > - if (WARN_ON_ONCE(map.m_pblk == NEW_ADDR)) > + pblk = map.m_pblk; > + if (map.m_multidev_dio && map.m_flags & F2FS_MAP_MAPPED) > + for (i = 0; i < sbi->s_ndevs; i++) > + if (FDEV(i).bdev == map.m_bdev) > + pblk += FDEV(i).start_blk; > + if (WARN_ON_ONCE(pblk == NEW_ADDR)) > return -EINVAL; > - if (WARN_ON_ONCE(map.m_pblk == COMPRESS_ADDR)) > + if (WARN_ON_ONCE(pblk == COMPRESS_ADDR)) > return -EINVAL; Shoudn't we check NEW_ADDR and COMPRESS_ADDR before multiple-device block address conversion? > > - if (map.m_pblk != NULL_ADDR) { > + if (pblk != NULL_ADDR) { How to distinguish NULL_ADDR and valid blkaddr 0? I guess it should check F2FS_MAP_MAPPED flag first? Thanks, > iomap->length = blks_to_bytes(inode, map.m_len); > iomap->type = IOMAP_MAPPED; > iomap->flags |= IOMAP_F_MERGED; > > _______________________________________________ > Linux-f2fs-devel mailing list > Linux-f2fs-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
On Tue, 19 Mar 2024 09:42:19 +0800, Yufeng Wang wrote:
> duplicated code in redo_fd_request(),
> unlock_fdc() function has the same code "do_floppy = NULL" inside.
>
>
Applied, thanks!
[1/1] floppy: remove duplicated code in redo_fd_request()
commit: 50171b8667733146f139c773d8f00866ceb4cee4
Best regards,
--
Jens Axboe
On Mon, 18 Mar 2024 22:00:22 +0000, Pavel Begunkov wrote:
> Mandate ctx locking for task_work. Then, remove aux CQE caches mostly
> used by multishot requests and post them directly into the CQ.
>
> It's leaving some of the pre existing issue_flags and state conversion
> non conformant chunks, which will need to clean up later.
>
> v3: pass IO_URING_F_COMPLETE_DEFER to the cmd cancellation path
> drop patch moving request cancellation list removal to tw
> drop all other ublk changes
>
> [...]
Applied, thanks!
[01/13] io_uring/cmd: move io_uring_try_cancel_uring_cmd()
commit: c877857e86396576260d12eaae2f777fa4fd835f
[02/13] io_uring/cmd: kill one issue_flags to tw conversion
commit: c6740905f9862b2780cc9a9a3e1714ea153d6c74
[03/13] io_uring/cmd: fix tw <-> issue_flags conversion
commit: 17c8e3f66f16256d33a10555d0a63d64405ab046
[04/13] io_uring/cmd: introduce io_uring_cmd_complete
commit: 23b0bed538ac9b73518c670925ebb64f0239b54f
[05/13] nvme/io_uring: don't hard code IO_URING_F_UNLOCKED
commit: 1a587b0d65d09d61bd8f0db728923ab68d8fb9c2
[06/13] io_uring/rw: avoid punting to io-wq directly
commit: 7f3b8125c3aee86b5dea06d9a9738b16aa55cbdd
[07/13] io_uring: force tw ctx locking
commit: 2a475207f98db597043251be32bb8f16d3617af9
[08/13] io_uring: remove struct io_tw_state::locked
commit: ccb464aeb6e563d1df179aacbb7c514369ceb8f0
[09/13] io_uring: refactor io_fill_cqe_req_aux
commit: 39c25ce47d211f4decc47f09f9561b8630aab84e
[10/13] io_uring: get rid of intermediate aux cqe caches
commit: 1a7520889e02de50c8334e215a3f187ff9a92456
[11/13] io_uring: remove current check from complete_post
commit: 7af89eaee7d17c2f15e483c859d4fcc09dda6dce
[12/13] io_uring: refactor io_req_complete_post()
commit: 838070b49a0b1466156661b85f6c97dc4033902b
[13/13] io_uring: clean up io_lockdep_assert_cq_locked
commit: 3cba2895da4a77b5f555f29821487db42f084324
Best regards,
--
Jens Axboe
On 3/18/24 21:43, Yu Kuai wrote:
> Hi,
>
> 在 2024/03/19 9:18, Yu Kuai 写道:
>> Hi,
>>
>> 在 2024/03/18 17:39, Christian Brauner 写道:
>>> On Sat, Mar 16, 2024 at 10:49:33AM +0800, Yu Kuai wrote:
>>>> Hi, Christian
>>>>
>>>> 在 2024/03/15 21:54, Christian Brauner 写道:
>>>>> On Fri, Mar 15, 2024 at 08:08:49PM +0800, Yu Kuai wrote:
>>>>>> Hi, Christian
>>>>>> Hi, Christoph
>>>>>> Hi, Jan
>>>>>>
>>>>>> Perhaps now is a good time to send a formal version of this set.
>>>>>> However, I'm not sure yet what branch should I rebase and send
>>>>>> this set.
>>>>>> Should I send to the vfs tree?
>>>>>
>>>>> Nearly all of it is in fs/ so I'd say yes.
>>>>> .
>>>>
>>>> I see that you just create a new branch vfs.fixes, perhaps can I rebase
>>>> this set against this branch?
>>>
>>> Please base it on vfs.super. I'll rebase it to v6.9-rc1 on Sunday.
>>
>> Okay, I just see that vfs.super doesn't contain commit
>> 1cdeac6da33f("btrfs: pass btrfs_device to btrfs_scratch_superblocks()"),
>> and you might need to fix the conflict at some point.
>
> And there is another problem, dm-vdo doesn't exist in vfs.super yet. Do
> you still want me to rebase here?
>
The dm-vdo changes don't appear to rely on earlier patches in the
series, so I think dm-vdo could incorporate the dm-vdo patch
independently from the rest of the series, if that would be helpful. (I
don't want to confuse things too much.) In that case it would go through
the dm tree with the rest of dm-vdo.
Matt
The issue has been fixed by this patch, pls ignore this report, thanks. https://lore.kernel.org/linux-block/CAHj4cs8F0KzdqDdJcOaTf2Nk4P7Dg1H8ooBFrZQM-iMwBx=OWw@mail.gmail.com/ On Mon, Mar 18, 2024 at 11:22 AM Yi Zhang <yi.zhang@redhat.com> wrote: > > Hi > CKI recently reported one 100% reproduced panic[2] during blktests > nbd/003 on mainline from Mar 12, We didn't bisect it, but the first > commit we hit the problem was[1], pls help check it. > > [1] > Commit message: Merge tag 'vfs-6.9.uuid' of > git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs (6.8.0, > mainline.kernel.org, 0f1a8766) > > [2] > [ 1958.972721] run blktests nbd/003 at 2024-03-17 00:17:54 > [ 1960.191937] mount_clear_soc: attempt to access beyond end of device > [ 1960.191937] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1960.192975] EXT4-fs (nbd0): unable to read superblock > [ 1960.194390] nbd0: detected capacity change from 0 to 20971520 > [ 1960.195259] block nbd0: shutting down sockets > [ 1960.196731] I/O error, dev nbd0, sector 0 op 0x0:(READ) flags 0x0 > phys_seg 4 prio class 0 > [ 1960.197458] Buffer I/O error on dev nbd0, logical block 0, async page read > [ 1960.197828] Buffer I/O error on dev nbd0, logical block 1, async page read > [ 1960.198176] Buffer I/O error on dev nbd0, logical block 2, async page read > [ 1960.198521] Buffer I/O error on dev nbd0, logical block 3, async page read > [ 1960.200421] I/O error, dev nbd0, sector 0 op 0x0:(READ) flags 0x0 > phys_seg 4 prio class 0 > [ 1960.200918] Buffer I/O error on dev nbd0, logical block 0, async page read > [ 1960.201272] Buffer I/O error on dev nbd0, logical block 1, async page read > [ 1960.201638] Buffer I/O error on dev nbd0, logical block 2, async page read > [ 1960.202004] Buffer I/O error on dev nbd0, logical block 3, async page read > [ 1960.202385] ldm_validate_partition_table(): Disk read failed. > [ 1960.203201] nbd0: unable to read partition table > [ 1960.203846] nbd0: partition table beyond EOD, truncated > [ 1960.204135] mount_clear_soc: attempt to access beyond end of device > [ 1960.204135] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1960.205131] EXT4-fs (nbd0): unable to read superblock > [ 1960.205951] mount_clear_soc: attempt to access beyond end of device > [ 1960.205951] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1960.207020] EXT4-fs (nbd0): unable to read superblock > [ 1960.207852] mount_clear_soc: attempt to access beyond end of device > [ 1960.207852] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1960.208991] EXT4-fs (nbd0): unable to read superblock > [ 1960.209915] mount_clear_soc: attempt to access beyond end of device > [ 1960.209915] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1960.211011] EXT4-fs (nbd0): unable to read superblock > [ 1960.211874] mount_clear_soc: attempt to access beyond end of device > [ 1960.211874] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1960.213030] EXT4-fs (nbd0): unable to read superblock > [ 1960.213940] mount_clear_soc: attempt to access beyond end of device > [ 1960.213940] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1960.215014] EXT4-fs (nbd0): unable to read superblock > [ 1960.215979] mount_clear_soc: attempt to access beyond end of device > [ 1960.215979] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1960.217080] EXT4-fs (nbd0): unable to read superblock > [ 1960.218108] mount_clear_soc: attempt to access beyond end of device > [ 1960.218108] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1960.219179] EXT4-fs (nbd0): unable to read superblock > [ 1960.220240] mount_clear_soc: attempt to access beyond end of device > [ 1960.220240] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1960.221301] EXT4-fs (nbd0): unable to read superblock > [ 1960.222232] EXT4-fs (nbd0): unable to read superblock > [ 1960.223184] EXT4-fs (nbd0): unable to read superblock > [ 1960.2515XT4-fs (nbd0): unable to read superblock > [ 1960.725161] EXT4-fs (nbd0): unable to read superblock > [ 1960.726466] EXT4-fs (nbd0): unable to read superblock > [ 1960.727608] EXT4-fs (nbd0): unable to read superblock > [ 1960.728735] EXT4-fs (nbd0): unable to read superblock > [ 1960.729936] EXT4-fs (nbd0): unable to read superblock > [ 1960.731384] EXT4-fs (nbd0): unable to read superblock > [ 1960.732549] EXT4-fs (nbd0): unable to read superblock > [ 1960.733705] EXT4-fs (nbd0): unable to read superblock > [ 1960.734684] EXT4-fs (nbd0): unable to read superblock > [ 1960.736129] EXT4-fs (nbd0): unable to read superblock > [ 1960.737279] EXT4-fs (nbd0): unable to read superblock > [ 1960.738602] EXT4-fs (nbd0): unable to read superblock > [ 1960.739782] EXT4-fs (nbd0): unable to read superblock > [ 1960.740977] EXT4-fs (nbd0): unable to read superblock > [ 1960.742091] EXT4-fs (nbd0): unable to read superblock > [ 1960.743224] EXT4-fs (nbd0): unable to read superblock > [ 1960.744431] EXT4-fs (nbd0): unable to read superblock > [ 1960.745712] EXT4-fs (nbd0): unable to read superblock > [ 1960.747001] EXT4-fs (nbd0): unable to read superblock > [ 1960.748272] EXT4-fs (nbd0): unable to read superblock > [ 1960.749417] EXT4-fs (nbd0): unable to read super[ 1961.240923] > EXT4-fs (nbd0): unable to read superblock > [ 1961.251356] EXT4-fs (nbd0): unable to read superblock > [ 1961.252550] EXT4-fs (nbd0): unable to read superblock > [ 1961.254150] EXT4-fs (nbd0): unable to read superblock > [ 1961.255535] EXT4-fs (nbd0): unable to read superblock > [ 1961.256591] EXT4-fs (nbd0): unable to read superblock > [ 1961.257787] EXT4-fs (nbd0): unable to read superblock > [ 1961.258931] EXT4-fs (nbd0): unable to read superblock > [ 1961.259970] EXT4-fs (nbd0): unable to read superblock > [ 1961.261323] EXT4-fs (nbd0): unable to read superblock > [ 1961.262494] EXT4-fs (nbd0): unable to read superblock > [ 1961.263715] EXT4-fs (nbd0): unable to read superblock > [ 1961.264991] EXT4-fs (nbd0): unable to read superblock > [ 1961.266122] EXT4-fs (nbd0): unable to read superblock > [ 1961.267279] EXT4-fs (nbd0): unable to read superblock > [ 1961.268437] EXT4-fs (nbd0): unable to read superblock > [ 1961.269543] EXT4-fs (nbd0): unable to read superblock > [ 1961.270535] EXT4-fs (nbd0): unable to read superblock > [ 1961.271606] EXT4-fs (nbd0): unable to read superblock > [ 1961.272626] EXT4-fs (nbd0): unable to read superblock > [ 1961.273679] EXT4-fs (nbd0): unable to read superblock > [ 1961.274721] EXT4-fs (nbd0): unable to read superblock[ 1961.769303] > EXT4-fs (nbd0): unable to read superblock > [ 1961.776594] EXT4-fs (nbd0): unable to read superblock > [ 1961.777954] EXT4-fs (nbd0): unable to read superblock > [ 1961.779495] EXT4-fs (nbd0): unable to read superblock > [ 1961.780668] EXT4-fs (nbd0): unable to read superblock > [ 1961.781779] EXT4-fs (nbd0): unable to read superblock > [ 1961.782660] EXT4-fs (nbd0): unable to read superblock > [ 1961.783670] EXT4-fs (nbd0): unable to read superblock > [ 1961.784746] EXT4-fs (nbd0): unable to read superblock > [ 1961.785656] EXT4-fs (nbd0): unable to read superblock > [ 1961.786988] EXT4-fs (nbd0): unable to read superblock > [ 1961.788270] EXT4-fs (nbd0): unable to read superblock > [ 1961.789463] EXT4-fs (nbd0): unable to read superblock > [ 1961.790684] EXT4-fs (nbd0): unable to read superblock > [ 1961.791758] EXT4-fs (nbd0): unable to read superblock > [ 1961.792764] EXT4-fs (nbd0): unable to read superblock > [ 1961.793864] EXT4-fs (nbd0): unable to read superblock > [ 1961.794883] EXT4-fs (nbd0): unable to read superblock > [ 1961.795889] EXT4-fs (nbd0): unable to read superblock > [ 1961.796912] EXT4-fs (nbd0): unable to read superblock > [ 1961.797982] EXT4-fs (nbd0): unable to read superblock > [ 1961.799208] EXT4-fs (nbd0): unable to read superblock > [ 1961.800292] EXT4-fs (nbd0): unable to read superblock > [ 1961.801355] EXT4-fs (nbd0): unable to read superblock > [ 1961.802389] EXT4-fperblock > [ 1962.303795] EXT4-fs (nbd0): unable to read superblock > [ 1962.305132] EXT4-fs (nbd0): unable to read superblock > [ 1962.306409] EXT4-fs (nbd0): unable to read superblock > [ 1962.307708] EXT4-fs (nbd0): unable to read superblock > [ 1962.308935] EXT4-fs (nbd0): unable to read superblock > [ 1962.310120] EXT4-fs (nbd0): unable to read superblock > [ 1962.311294] EXT4-fs (nbd0): unable to read superblock > [ 1962.312513] EXT4-fs (nbd0): unable to read superblock > [ 1962.313702] EXT4-fs (nbd0): unable to read superblock > [ 1962.314682] EXT4-fs (nbd0): unable to read superblock > [ 1962.315748] EXT4-fs (nbd0): unable to read superblock > [ 1962.316891] EXT4-fs (nbd0): unable to read superblock > [ 1962.318041] EXT4-fs (nbd0): unable to read superblock > [ 1962.319213] EXT4-fs (nbd0): unable to read superblock > [ 1962.320443] EXT4-fs (nbd0): unable to read superblock > [ 1962.321536] EXT4-fs (nbd0): unable to read superblock > [ 1962.322579] EXT4-fs (nbd0): unable to read superblock > [ 1962.323626] EXT4-fs (nbd0): unable to read superblock > [ 1962.324674] EXT4-fs (nbd0): unable to read superblock > [ 1962.325620] EXT4-fs (nbd0): unable to read superblock > [ 1962.326700] EXT4-fs (nbd0): unable to read superblock > [ 1962.327640] EXT4-fperblock > [ 1962.828982] EXT4-fs (nbd0): unable to read superblock > [ 1962.830270] EXT4-fs (nbd0): unable to read superblock > [ 1962.831500] EXT4-fs (nbd0): unable to read superblock > [ 1962.832782] EXT4-fs (nbd0): unable to read superblock > [ 1962.833862] EXT4-fs (nbd0): unable to read superblock > [ 1962.835039] EXT4-fs (nbd0): unable to read superblock > [ 1962.836420] EXT4-fs (nbd0): unable to read superblock > [ 1962.837434] EXT4-fs (nbd0): unable to read superblock > [ 1962.838755] EXT4-fs (nbd0): unable to read superblock > [ 1962.839996] EXT4-fs (nbd0): unable to read superblock > [ 1962.841161] EXT4-fs (nbd0): unable to read superblock > [ 1962.842484] EXT4-fs (nbd0): unable to read superblock > [ 1962.843745] EXT4-fs (nbd0): unable to read superblock > [ 1962.844748] EXT4-fs (nbd0): unable to read superblock > [ 1962.845678] EXT4-fs (nbd0): unable to read superblock > [ 1962.846676] EXT4-fs (nbd0): unable to read superblock > [ 1962.847650] EXT4-fs (nbd0): unable to read superblock > [ 1962.848708] EXT4-fs (nbd0): unable to read superblock > [ 1962.849657] EXT4-fs (nbd0): unable to read superblock > [ 1962.850658] EXT4-fs (nbd0): unable to read superblock > [ 1962.851653] EXT4-fs (nbd0): unable to read superblock > [ 1962.852571] EXT4-fs (nbd0): unable to read supeXT4-fs (nbd0): > unable to read superblock > [ 1963.254601] EXT4-fs (nbd0): unable to read superblock > [ 1963.255816] EXT4-fs (nbd0): unable to read superblock > [ 1963.257007] EXT4-fs (nbd0): unable to read superblock > [ 1963.258287] EXT4-fs (nbd0): unable to read superblock > [ 1963.259540] EXT4-fs (nbd0): unable to read superblock > [ 1963.260949] EXT4-fs (nbd0): unable to read superblock > [ 1963.262073] EXT4-fs (nbd0): unable to read superblock > [ 1963.263255] EXT4-fs (nbd0): unable to read superblock > [ 1963.264556] EXT4-fs (nbd0): unable to read superblock > [ 1963.265629] EXT4-fs (nbd0): unable to read superblock > [ 1963.266712] EXT4-fs (nbd0): unable to read superblock > [ 1963.267759] EXT4-fs (nbd0): unable to read superblock > [ 1963.268781] EXT4-fs (nbd0): unable to read superblock > [ 1963.269994] EXT4-fs (nbd0): unable to read superblock > [ 1963.271123] EXT4-fs (nbd0): unable to read superblock > [ 1963.272488] EXT4-fs (nbd0): unable to read superblock > [ 1963.273740] EXT4-fs (nbd0): unable to read superblock > [ 1963.274963] EXT4-fs (nbd0): unable to read superblock > [ 1963.276084] EXT4-fs (nbd0): unable to read superblock > [ 1963.277491] EXT4-fs (nperblock > [ 1963.778803] EXT4-fs (nbd0): unable to read superblock > [ 1963.780006] EXT4-fs (nbd0): unable to read superblock > [ 1963.781222] EXT4-fs (nbd0): unable to read superblock > [ 1963.782590] EXT4-fs (nbd0): unable to read superblock > [ 1963.783705] EXT4-fs (nbd0): unable to read superblock > [ 1963.784871] EXT4-fs (nbd0): unable to read superblock > [ 1963.786064] EXT4-fs (nbd0): unable to read superblock > [ 1963.787274] EXT4-fs (nbd0): unable to read superblock > [ 1963.788490] EXT4-fs (nbd0): unable to read superblock > [ 1963.789886] EXT4-fs (nbd0): unable to read superblock > [ 1963.791190] EXT4-fs (nbd0): unable to read superblock > [ 1963.792375] EXT4-fs (nbd0): unable to read superblock > [ 1963.793567] EXT4-fs (nbd0): unable to read superblock > [ 1963.795024] EXT4-fs (nbd0): unable to read superblock > [ 1963.796257] EXT4-fs (nbd0): unable to read superblock > [ 1963.797488] EXT4-fs (nbd0): unable to read superblock > [ 1963.798578] EXT4-fs (nbd0): unable to read superblock > [ 1963.799581] EXT4-fs (nbd0): unable to read superblock > [ 1963.800628] EXT4-fs (nbd0): unable to read superblock > [ 1963.801746] EXT4-fs (nbd0): unable to read superblock > [ 1963.802954] EXT4-fs (nbd0): unable to read superblock > [ 1963XT4-fs (nbd0): unable to read superblock > [ 1964.304751] EXT4-fs (nbd0): unable to read superblock > [ 1964.305880] EXT4-fs (nbd0): unable to read superblock > [ 1964.307073] EXT4-fs (nbd0): unable to read superblock > [ 1964.308417] EXT4-fs (nbd0): unable to read superblock > [ 1964.309567] EXT4-fs (nbd0): unable to read superblock > [ 1964.310702] EXT4-fs (nbd0): unable to read superblock > [ 1964.311732] EXT4-fs (nbd0): unable to read superblock > [ 1964.312797] EXT4-fs (nbd0): unable to read superblock > [ 1964.313966] EXT4-fs (nbd0): unable to read superblock > [ 1964.315098] EXT4-fs (nbd0): unable to read superblock > [ 1964.316325] EXT4-fs (nbd0): unable to read superblock > [ 1964.317292] EXT4-fs (nbd0): unable to read superblock > [ 1964.318254] EXT4-fs (nbd0): unable to read superblock > [ 1964.319484] EXT4-fs (nbd0): unable to read superblock > [ 1964.320690] EXT4-fs (nbd0): unable to read superblock > [ 1964.321654] EXT4-fs (nbd0): unable to read superblock > [ 1964.322677] EXT4-fs (nbd0): unable to read superblock > [ 1964.323821] EXT4-fs (nbd0): unable to read superblock > [ 1964.325088] EXT4-fs (nbd0): unable to read s[ 1964.826671] EXT4-fs > (nbd0): unable to read superblock > [ 1964.827837] EXT4-fs (nbd0): unable to read superblock > [ 1964.829110] EXT4-fs (nbd0): unable to read superblock > [ 1964.830370] EXT4-fs (nbd0): unable to read superblock > [ 1964.831591] EXT4-fs (nbd0): unable to read superblock > [ 1964.832720] EXT4-fs (nbd0): unable to read superblock > [ 1964.833711] EXT4-fs (nbd0): unable to read superblock > [ 1964.834904] EXT4-fs (nbd0): unable to read superblock > [ 1964.836119] EXT4-fs (nbd0): unable to read superblock > [ 1964.837462] EXT4-fs (nbd0): unable to read superblock > [ 1964.838563] EXT4-fs (nbd0): unable to read superblock > [ 1964.839732] EXT4-fs (nbd0): unable to read superblock > [ 1964.841018] EXT4-fs (nbd0): unable to read superblock > [ 1964.842147] EXT4-fs (nbd0): unable to read superblock > [ 1964.843357] EXT4-fs (nbd0): unable to read superblock > [ 1964.844368] EXT4-fs (nbd0): unable to read superblock > [ 1964.845506] EXT4-fs (nbd0): unable to read superblock > [ 1964.846639] EXT4-fs (nbd0): unable to read superblock > [ 1964.847537] EXT4-fs (nbd0): unable to read superblock > [ 1964.848711] EXT4-fs (nbd0): unable to read superblock > [ 1964.879io_check_eod: 226 callbacks suppressed > [ 1965.302867] mount_clear_soc: attempt to access beyond end of device > [ 1965.302867] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1965.351009] EXT4-fs (nbd0): unable to read superblock > [ 1965.352242] mount_clear_soc: attempt to access beyond end of device > [ 1965.352242] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1965.353307] EXT4-fs (nbd0): unable to read superblock > [ 1965.354610] mount_clear_soc: attempt to access beyond end of device > [ 1965.354610] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1965.355613] EXT4-fs (nbd0): unable to read superblock > [ 1965.356798] mount_clear_soc: attempt to access beyond end of device > [ 1965.356798] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1965.357890] EXT4-fs (nbd0): unable to read superblock > [ 1965.358943] mount_clear_soc: attempt to access beyond end of device > [ 1965.358943] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1965.360117] EXT4-fs (nbd0): unable to read superblock > [ 1965.361191] mount_clear_soc: attempt to access beyond end of device > [ 1965.361191] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1965.362233] EXT4-fs (nbd0): unable to read superblock > [ 1965.363217] mount_clear_soc: attempt to access beyond end of device > [nr_sectors = 2 limit=0 > [ 1965.864302] EXT4-fs (nbd0): unable to read superblock > [ 1965.865571] mount_clear_soc: attempt to access beyond end of device > [ 1965.865571] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1965.866591] EXT4-fs (nbd0): unable to read superblock > [ 1965.867786] mount_clear_soc: attempt to access beyond end of device > [ 1965.867786] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1965.868906] EXT4-fs (nbd0): unable to read superblock > [ 1965.870151] EXT4-fs (nbd0): unable to read superblock > [ 1965.871487] EXT4-fs (nbd0): unable to read superblock > [ 1965.872595] EXT4-fs (nbd0): unable to read superblock > [ 1965.873736] EXT4-fs (nbd0): unable to read superblock > [ 1965.874997] EXT4-fs (nbd0): unable to read superblock > [ 1965.876149] EXT4-fs (nbd0): unable to read superblock > [ 1965.877479] EXT4-fs (nbd0): unable to read superblock > [ 1965.879177] EXT4-fs (nbd0): unable to read superblock > [ 1965.880498] EXT4-fs (nbd0): unable to read superblock > [ 1965.881584] EXT4-fs (nbd0): unable to read superblock > [ 1965.882842] EXT4-fs (nbd0): unable toperblock > [ 1966.384383] EXT4-fs (nbd0): unable to read superblock > [ 1966.385648] EXT4-fs (nbd0): unable to read superblock > [ 1966.386939] EXT4-fs (nbd0): unable to read superblock > [ 1966.388125] EXT4-fs (nbd0): unable to read superblock > [ 1966.389459] EXT4-fs (nbd0): unable to read superblock > [ 1966.390748] EXT4-fs (nbd0): unable to read superblock > [ 1966.392003] EXT4-fs (nbd0): unable to read superblock > [ 1966.393201] EXT4-fs (nbd0): unable to read superblock > [ 1966.394544] EXT4-fs (nbd0): unable to read superblock > [ 1966.395743] EXT4-fs (nbd0): unable to read superblock > [ 1966.396833] EXT4-fs (nbd0): unable to read superblock > [ 1966.397799] EXT4-fs (nbd0): unable to read superblock > [ 1966.398971] EXT4-fs (nbd0): unable to read superblock > [ 1966.400179] EXT4-fs (nbd0): unable to read superblock > [ 1966.401383] EXT4-fs (nbd0): unable to read superblock > [ 1966.402472] EXT4-fs (nbd0): unable to read superblock > [ 1966.403730] EXT4-fs (nbd0): unable to read superblock > [ 1966.404791] EXT4-fs (nbd0): unable to read superblock > [ 1966.405855] EXT4-fs (nbd0): unable to read superblock > [ 196XT4-fs (nbd0): unable to read superblock > [ 1966.807515] EXT4-fs (nbd0): unable to read superblock > [ 1966.808814] EXT4-fs (nbd0): unable to read superblock > [ 1966.810034] EXT4-fs (nbd0): unable to read superblock > [ 1966.811238] EXT4-fs (nbd0): unable to read superblock > [ 1966.812577] EXT4-fs (nbd0): unable to read superblock > [ 1966.813679] EXT4-fs (nbd0): unable to read superblock > [ 1966.814928] EXT4-fs (nbd0): unable to read superblock > [ 1966.816167] EXT4-fs (nbd0): unable to read superblock > [ 1966.817551] EXT4-fs (nbd0): unable to read superblock > [ 1966.818796] EXT4-fs (nbd0): unable to read superblock > [ 1966.819914] EXT4-fs (nbd0): unable to read superblock > [ 1966.821035] EXT4-fs (nbd0): unable to read superblock > [ 1966.822430] EXT4-fs (nbd0): unable to read superblock > [ 1966.823800] EXT4-fs (nbd0): unable to read superblock > [ 1966.825156] EXT4-fs (nbd0): unable to read superblock > [ 1966.826454] EXT4-fs (nbd0): unable to read superblock > [ 1966.827617] EXT4-fs (nbd0): unable to read superblock > [ 1966.828804] EXT4-fs (nbd0): unable to read superblock > [ 1966.829741] EXT4-fs (nbd0): unable to read superblock > [ 1966.830956] EXT4-fs (nbperblock > [ 1967.332488] EXT4-fs (nbd0): unable to read superblock > [ 1967.333868] EXT4-fs (nbd0): unable to read superblock > [ 1967.335094] EXT4-fs (nbd0): unable to read superblock > [ 1967.336428] EXT4-fs (nbd0): unable to read superblock > [ 1967.337695] EXT4-fs (nbd0): unable to read superblock > [ 1967.338896] EXT4-fs (nbd0): unable to read superblock > [ 1967.340071] EXT4-fs (nbd0): unable to read superblock > [ 1967.341248] EXT4-fs (nbd0): unable to read superblock > [ 1967.342619] EXT4-fs (nbd0): unable to read superblock > [ 1967.343894] EXT4-fs (nbd0): unable to read superblock > [ 1967.345060] EXT4-fs (nbd0): unable to read superblock > [ 1967.346474] EXT4-fs (nbd0): unable to read superblock > [ 1967.347792] EXT4-fs (nbd0): unable to read superblock > [ 1967.349003] EXT4-fs (nbd0): unable to read superblock > [ 1967.350395] EXT4-fs (nbd0): unable to read superblock > [ 1967.351747] EXT4-fs (nbd0): unable to read superblock > [ 1967.352737] EXT4-fs (nbd0): unable to read superblock > [ 1967.353756] EXT4-fs (nbd0): unable to read superblock > [ 1967.355008] EXT4-fs (nbd0): unable to read superblock > [ 1967.356323] EXT4-fs (nbd0): unable to read superblock > [ 1967.357618] EXT4-fs (nbdperblock > [ 1967.858991] EXT4-fs (nbd0): unable to read superblock > [ 1967.860160] EXT4-fs (nbd0): unable to read superblock > [ 1967.861756] EXT4-fs (nbd0): unable to read superblock > [ 1967.863055] EXT4-fs (nbd0): unable to read superblock > [ 1967.864493] EXT4-fs (nbd0): unable to read superblock > [ 1967.865762] EXT4-fs (nbd0): unable to read superblock > [ 1967.867017] EXT4-fs (nbd0): unable to read superblock > [ 1967.868449] EXT4-fs (nbd0): unable to read superblock > [ 1967.869716] EXT4-fs (nbd0): unable to read superblock > [ 1967.871118] EXT4-fs (nbd0): unable to read superblock > [ 1967.872507] EXT4-fs (nbd0): unable to read superblock > [ 1967.873794] EXT4-fs (nbd0): unable to read superblock > [ 1967.875087] EXT4-fs (nbd0): unable to read superblock > [ 1967.876262] EXT4-fs (nbd0): unable to read superblock > [ 1967.877604] EXT4-fs (nbd0): unable to read superblock > [ 1967.879644] EXT4-fs (nbd0): unable to read superblock > [ 1967.880867] EXT4-fs (nbd0): unable to read superblock > [ 1967.882136] EXT4-fs (nbd0): unable to read superblock > [ 1967.883483] EXT4-fs (nbd0): unable to read superblock > [ 1967.884715] EXT4-fs (nbd0): unable to read superblock > [ 1967.886040] EXT4-fs (nbd0): unable to read superblock > [ 1967.887220] EXT4-fs (nbd0): unable to read superblock > [ 1967.888566] EXT4-fs (nbd0): unable to read superblock > [ 1967.889673] EXT4-fs (nbd0): unable to read superblock > [ 1967.890897] EXT4-fs (nbd0): unable to read superblock > [ 1967.892052] EXT4-fs (nbd0):nable to read superblock > [ 1968.393772] EXT4-fs (nbd0): unable to read superblock > [ 1968.395087] EXT4-fs (nbd0): unable to read superblock > [ 1968.396414] EXT4-fs (nbd0): unable to read superblock > [ 1968.397752] EXT4-fs (nbd0): unable to read superblock > [ 1968.399036] EXT4-fs (nbd0): unable to read superblock > [ 1968.400338] EXT4-fs (nbd0): unable to read superblock > [ 1968.401699] EXT4-fs (nbd0): unable to read superblock > [ 1968.402928] EXT4-fs (nbd0): unable to read superblock > [ 1968.404187] EXT4-fs (nbd0): unable to read superblock > [ 1968.405561] EXT4-fs (nbd0): unable to read superblock > [ 1968.406862] EXT4-fs (nbd0): unable to read superblock > [ 1968.408117] EXT4-fs (nbd0): unable to read superblock > [ 1968.409472] EXT4-fs (nbd0): unable to read superblock > [ 1968.410806] EXT4-fs (nbd0): unable to read superblock > [ 1968.412001] EXT4-fs (nbd0): unable to read superblock > [ 1968.413062] EXT4-fs (nbd0): unable to read superblock > [ 1968.414294] EXT4-fs (nbd0): unable to read superblock > [ 1968.415574] EXT4-fs (nbd0): unable to read superblock > [ 1968.416864] EXT4-fs (nbd0): unable to read superblock > [ 1968.418182] EXT4-fs (nbd0): unable to read superblock > [ 1968.419594] EXT4-fs (nbd0): unable to read superblock > [ 1968.XT4-fs (nbd0): unable to read superblock > [ 1968.921536] EXT4-fs (nbd0): unable to read superblock > [ 1968.922607] EXT4-fs (nbd0): unable to read superblock > [ 1968.923842] EXT4-fs (nbd0): unable to read superblock > [ 1968.925111] EXT4-fs (nbd0): unable to read superblock > [ 1968.926578] EXT4-fs (nbd0): unable to read superblock > [ 1968.927822] EXT4-fs (nbd0): unable to read superblock > [ 1968.928951] EXT4-fs (nbd0): unable to read superblock > [ 1968.930040] EXT4-fs (nbd0): unable to read superblock > [ 1968.931187] EXT4-fs (nbd0): unable to read superblock > [ 1968.932392] EXT4-fs (nbd0): unable to read superblock > [ 1968.933534] EXT4-fs (nbd0): unable to read superblock > [ 1968.934919] EXT4-fs (nbd0): unable to read superblock > [ 1968.936053] EXT4-fs (nbd0): unable to read superblock > [ 1968.937189] EXT4-fs (nbd0): unable to read superblock > [ 1968.938516] EXT4-fs (nbd0): unable to read superblock > [ 1968.939730] EXT4-fs (nbd0): unable to read superblock > [ 1968.940939] EXT4-fs (nbd0): unable to read superblock > [ 1968.942064] EXT4-fs (nbd0): unable to read superblock > [ 1968.943292] EXT4-fs (nbd0): unable to read superblock > [ 1968.944552] EXT4-fs (nbd0): unable to read superb[ 1969.434709] > EXT4-fs (nbd0): unable to read superblock > [ 1969.446413] EXT4-fs (nbd0): unable to read superblock > [ 1969.447651] EXT4-fs (nbd0): unable to read superblock > [ 1969.448940] EXT4-fs (nbd0): unable to read superblock > [ 1969.450019] EXT4-fs (nbd0): unable to read superblock > [ 1969.451324] EXT4-fs (nbd0): unable to read superblock > [ 1969.452568] EXT4-fs (nbd0): unable to read superblock > [ 1969.453692] EXT4-fs (nbd0): unable to read superblock > [ 1969.454829] EXT4-fs (nbd0): unable to read superblock > [ 1969.456246] EXT4-fs (nbd0): unable to read superblock > [ 1969.457578] EXT4-fs (nbd0): unable to read superblock > [ 1969.458841] EXT4-fs (nbd0): unable to read superblock > [ 1969.460127] EXT4-fs (nbd0): unable to read superblock > [ 1969.461502] EXT4-fs (nbd0): unable to read superblock > [ 1969.462804] EXT4-fs (nbd0): unable to read superblock > [ 1969.463860] EXT4-fs (nbd0): unable to read superblock > [ 1969.465039] EXT4-fs (nbd0): unable to read superblock > [ 1969.465989] EXT4-fs (nbd0): unable to read superblock > [ 1969.467005] EXT4-fs (nbd0): unable to read superblock > [ 1969.468098] EXT4-fs (nbd0): unable to read superblock > [ 1969.469265] EXT4-fs (nbd0): unable to read superblock > [ 1969.470522] EXT4-fs (nbd0): unable to read superblock > [ 1969.471633] EXT4-fs (nbd0): unable to read superblocXT4-fs (nbd0): > unable to read superblock > [ 1969.873378] EXT4-fs (nbd0): unable to read superblock > [ 1969.875075] EXT4-fs (nbd0): unable to read superblock > [ 1969.876415] EXT4-fs (nbd0): unable to read superblock > [ 1969.878475] EXT4-fs (nbd0): unable to read superblock > [ 1969.879625] EXT4-fs (nbd0): unable to read superblock > [ 1969.881027] EXT4-fs (nbd0): unable to read superblock > [ 1969.882237] EXT4-fs (nbd0): unable to read superblock > [ 1969.883698] EXT4-fs (nbd0): unable to read superblock > [ 1969.884947] EXT4-fs (nbd0): unable to read superblock > [ 1969.886205] EXT4-fs (nbd0): unable to read superblock > [ 1969.887415] EXT4-fs (nbd0): unable to read superblock > [ 1969.888692] EXT4-fs (nbd0): unable to read superblock > [ 1969.889891] EXT4-fs (nbd0): unable to read superblock > [ 1969.891025] EXT4-fs (nbd0): unable to read superblock > [ 1969.892109] EXT4-fs (nbd0): unable to read superblock > [ 1969.893421] EXT4-fs (nbd0): unable to read superblock > [ 1969.894754] EXT4-fs (nbd0): unable to read superblock > [ 1969.895946] EXT4-fs (nbd0): unable to read superblock > [ 1969.897157] EXT4-fs (nbd0): unable to read superblock > [ 1969.898387] EXT4-fs (nbd0): unable to read superblock > [ 1969.899713] EXT4-fs (nbd0): unable to read sperblock > [ 1970.401549] bio_check_eod: 210 callbacks suppressed > [ 1970.401554] mount_clear_soc: attempt to access beyond end of device > [ 1970.401554] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1970.403386] EXT4-fs (nbd0): unable to read superblock > [ 1970.404592] mount_clear_soc: attempt to access beyond end of device > [ 1970.404592] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1970.405660] EXT4-fs (nbd0): unable to read superblock > [ 1970.406944] mount_clear_soc: attempt to access beyond end of device > [ 1970.406944] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1970.408074] EXT4-fs (nbd0): unable to read superblock > [ 1970.409264] mount_clear_soc: attempt to access beyond end of device > [ 1970.409264] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1970.410520] EXT4-fs (nbd0): unable to read superblock > [ 1970.411704] mount_clear_soc: attempt to access beyond end of device > [ 1970.411704] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1970.412851] EXT4-fs (nbd0): unable to read superblock > [ 1970.414014] mount_clear_soc: attempt to access beyond end of device > [ 1970.414014] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1970.415097] EXT4-fs (nbd0): unable to read superblock > [ 1970.416330] mount_clear_soc: attempt to acces67120] nbd0: rw=4096, > sector=2, nr_sectors = 2 limit=0 > [ 1970.917990] EXT4-fs (nbd0): unable to read superblock > [ 1970.919273] mount_clear_soc: attempt to access beyond end of device > [ 1970.919273] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1970.920541] EXT4-fs (nbd0): unable to read superblock > [ 1970.921894] mount_clear_soc: attempt to access beyond end of device > [ 1970.921894] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1970.922979] EXT4-fs (nbd0): unable to read superblock > [ 1970.924048] EXT4-fs (nbd0): unable to read superblock > [ 1970.925234] EXT4-fs (nbd0): unable to read superblock > [ 1970.926397] EXT4-fs (nbd0): unable to read superblock > [ 1970.927619] EXT4-fs (nbd0): unable to read superblock > [ 1970.928881] EXT4-fs (nbd0): unable to read superblock > [ 1970.930101] EXT4-fs (nbd0): unable to read superblock > [ 1970.931216] EXT4-fs (nbd0): unable to read superblock > [ 1970.932587] EXT4-fs (nbd0): unable to read superblock > [ 1970.933800] EXT4-fs (nbd0): unable to read superblock > [ 1970.934921] EXT4-fs (nbd0): unable to read superblock > [ 1970.936074] EXT4-fs (nbd0): unable to read superblock > [ 1970.937272] EXT4-fs (nbd0): unable to read superblock > [ 1970.938518] EXT4-fs (nbd0): unable to read super[ 1971.439977] > EXT4-fs (nbd0): unable to read superblock > [ 1971.441138] EXT4-fs (nbd0): unable to read superblock > [ 1971.442545] EXT4-fs (nbd0): unable to read superblock > [ 1971.443886] EXT4-fs (nbd0): unable to read superblock > [ 1971.445055] EXT4-fs (nbd0): unable to read superblock > [ 1971.446192] EXT4-fs (nbd0): unable to read superblock > [ 1971.447646] EXT4-fs (nbd0): unable to read superblock > [ 1971.448964] EXT4-fs (nbd0): unable to read superblock > [ 1971.450108] EXT4-fs (nbd0): unable to read superblock > [ 1971.451538] EXT4-fs (nbd0): unable to read superblock > [ 1971.452877] EXT4-fs (nbd0): unable to read superblock > [ 1971.454019] EXT4-fs (nbd0): unable to read superblock > [ 1971.455126] EXT4-fs (nbd0): unable to read superblock > [ 1971.456541] EXT4-fs (nbd0): unable to read superblock > [ 1971.457775] EXT4-fs (nbd0): unable to read superblock > [ 1971.458936] EXT4-fs (nbd0): unable to read superblock > [ 1971.460117] EXT4-fs (nbd0): unable to read superblock > [ 1971.461490] EXT4-fs (nbd0): unable to read superblock > [ 1971.462596] EXT4-fs (nbd0): unable to read superblock > [ 1971.463902] EXT4-fs (nbd0): unable to read superblock > [ 1971.465182] EXT4-fs (nbd0): unable to read superblock > [ 1971.466450] EXT4-fs (nbd0): unable to read superblock > [ 1971.467630] EXT4-fs (nbd0): unable to read superbl[ 1971.967075] > EXT4-fs (nbd0): unable to read superblock > [ 1971.969578] EXT4-fs (nbd0): unable to read superblock > [ 1971.970836] EXT4-fs (nbd0): unable to read superblock > [ 1971.972149] EXT4-fs (nbd0): unable to read superblock > [ 1971.973543] EXT4-fs (nbd0): unable to read superblock > [ 1971.974864] EXT4-fs (nbd0): unable to read superblock > [ 1971.975870] EXT4-fs (nbd0): unable to read superblock > [ 1971.976890] EXT4-fs (nbd0): unable to read superblock > [ 1971.978414] EXT4-fs (nbd0): unable to read superblock > [ 1971.979558] EXT4-fs (nbd0): unable to read superblock > [ 1971.980639] EXT4-fs (nbd0): unable to read superblock > [ 1971.981734] EXT4-fs (nbd0): unable to read superblock > [ 1971.982758] EXT4-fs (nbd0): unable to read superblock > [ 1971.983869] EXT4-fs (nbd0): unable to read superblock > [ 1971.984783] EXT4-fs (nbd0): unable to read superblock > [ 1971.986014] EXT4-fs (nbd0): unable to read superblock > [ 1971.986920] EXT4-fs (nbd0): unable to read superblock > [ 1971.987864] EXT4-fs (nbd0): unable to read superblock > [ 1971.989016] EXT4-fs (nbd0): unable to read superblock > [ 1971.989911] EXT4-fs (nbd0): unable to read superblock > [ 1971.990761] EXT4-fs (nbd0): unable [ 1972.492289] EXT4-fs (nbd0): > unable to read superblock > [ 1972.493687] EXT4-fs (nbd0): unable to read superblock > [ 1972.494988] EXT4-fs (nbd0): unable to read superblock > [ 1972.496177] EXT4-fs (nbd0): unable to read superblock > [ 1972.497656] EXT4-fs (nbd0): unable to read superblock > [ 1972.498883] EXT4-fs (nbd0): unable to read superblock > [ 1972.500168] EXT4-fs (nbd0): unable to read superblock > [ 1972.501586] EXT4-fs (nbd0): unable to read superblock > [ 1972.502905] EXT4-fs (nbd0): unable to read superblock > [ 1972.504588] EXT4-fs (nbd0): unable to read superblock > [ 1972.505905] EXT4-fs (nbd0): unable to read superblock > [ 1972.507266] EXT4-fs (nbd0): unable to read superblock > [ 1972.508695] EXT4-fs (nbd0): unable to read superblock > [ 1972.509969] EXT4-fs (nbd0): unable to read superblock > [ 1972.511141] EXT4-fs (nbd0): unable to read superblock > [ 1972.512423] EXT4-fs (nbd0): unable to read superblock > [ 1972.513625] EXT4-fs (nbd0): unable to read superblock > [ 1972.514714] EXT4-fs (nbd0): unable to read superblock > [ 1972.516068] EXT4-fs (nbd0): unable to read superblock > [ 1972.517208] EXT4-fs (nbd0): unable to read superblock > [ 1972.548XT4-fs (nbd0): unable to read superblock > [ 1973.019078] EXT4-fs (nbd0): unable to read superblock > [ 1973.020565] EXT4-fs (nbd0): unable to read superblock > [ 1973.021932] EXT4-fs (nbd0): unable to read superblock > [ 1973.023134] EXT4-fs (nbd0): unable to read superblock > [ 1973.024605] EXT4-fs (nbd0): unable to read superblock > [ 1973.025755] EXT4-fs (nbd0): unable to read superblock > [ 1973.026872] EXT4-fs (nbd0): unable to read superblock > [ 1973.028181] EXT4-fs (nbd0): unable to read superblock > [ 1973.029412] EXT4-fs (nbd0): unable to read superblock > [ 1973.030657] EXT4-fs (nbd0): unable to read superblock > [ 1973.031930] EXT4-fs (nbd0): unable to read superblock > [ 1973.033112] EXT4-fs (nbd0): unable to read superblock > [ 1973.034274] EXT4-fs (nbd0): unable to read superblock > [ 1973.035467] EXT4-fs (nbd0): unable to read superblock > [ 1973.036672] EXT4-fs (nbd0): unable to read superblock > [ 1973.037878] EXT4-fs (nbd0): unable to read superblock > [ 1973.039075] EXT4-fs (nbd0): unable to read superblock > [ 1973.040057] EXT4-fs (nbd0): unable to read superblock > [ 1973.041061] EXT4-fs (nbd0): unable to read superblock > [ 1973.042092] EXT4-fs (nbd0): unable to read superblock > [ 1973.043203] EXT4-fs (nbd0): unable to read superblock > [ 1973.044258] EXT4-fs (nbd0): unable to read superblock > [ 1973.045557] EXT4-fs (nbd0): unable t[ 1973.430952] EXT4-fs (nbd0): > unable to read superblock > [ 1973.447205] EXT4-fs (nbd0): unable to read superblock > [ 1973.448741] EXT4-fs (nbd0): unable to read superblock > [ 1973.449877] EXT4-fs (nbd0): unable to read superblock > [ 1973.450919] EXT4-fs (nbd0): unable to read superblock > [ 1973.452192] EXT4-fs (nbd0): unable to read superblock > [ 1973.453600] EXT4-fs (nbd0): unable to read superblock > [ 1973.454682] EXT4-fs (nbd0): unable to read superblock > [ 1973.455893] EXT4-fs (nbd0): unable to read superblock > [ 1973.457170] EXT4-fs (nbd0): unable to read superblock > [ 1973.458317] EXT4-fs (nbd0): unable to read superblock > [ 1973.459596] EXT4-fs (nbd0): unable to read superblock > [ 1973.461197] EXT4-fs (nbd0): unable to read superblock > [ 1973.462475] EXT4-fs (nbd0): unable to read superblock > [ 1973.463621] EXT4-fs (nbd0): unable to read superblock > [ 1973.465069] EXT4-fs (nbd0): unable to read superblock > [ 1973.466208] EXT4-fs (nbd0): unable to read superblock > [ 1973.467558] EXT4-fs (nbd0): unable to read superblock > [ 1973.469073] EXT4-fs (nbd0): unable to read superblock > [ 1973.470293] EXT4-fs (nbd0): unable to read superblock > [ 1973.471588] EXT4-fs (nbd0): unable to read superblock > [ 1973.472837] EXT4-fs (nbd0): unable to read superblock > [ 1973.473753] EXT4-fs (nbd0): unable to read superblock > [ 1973.474920] EXT4-fs (nbd0): unable to read superblock > [ 1973.475938] EXT4-fs (nbd0): unable to read superblock > [ 1973.477404] EXT4-fs (nbd0): unable to[ 1973.979001] EXT4-fs (nbd0): > unable to read superblock > [ 1973.980320] EXT4-fs (nbd0): unable to read superblock > [ 1973.981812] EXT4-fs (nbd0): unable to read superblock > [ 1973.983017] EXT4-fs (nbd0): unable to read superblock > [ 1973.984322] EXT4-fs (nbd0): unable to read superblock > [ 1973.985738] EXT4-fs (nbd0): unable to read superblock > [ 1973.987155] EXT4-fs (nbd0): unable to read superblock > [ 1973.988483] EXT4-fs (nbd0): unable to read superblock > [ 1973.990115] EXT4-fs (nbd0): unable to read superblock > [ 1973.991275] EXT4-fs (nbd0): unable to read superblock > [ 1973.992552] EXT4-fs (nbd0): unable to read superblock > [ 1973.993765] EXT4-fs (nbd0): unable to read superblock > [ 1973.994944] EXT4-fs (nbd0): unable to read superblock > [ 1973.996145] EXT4-fs (nbd0): unable to read superblock > [ 1973.997285] EXT4-fs (nbd0): unable to read superblock > [ 1973.998482] EXT4-fs (nbd0): unable to read superblock > [ 1973.999627] EXT4-fs (nbd0): unable to read superblock > [ 1974.000697] EXT4-fs (nbd0): unable to read superblock > [ 1974.001706] EXT4-fs (nbd0): unable to read superblock > [ 1974.002880] EXT4-fs (nbd0): unable to read superblock > [ 1974.03[ 1974.475084] EXT4-fs (nbd0): unable to read superblock > [ 1974.505082] EXT4-fs (nbd0): unable to read superblock > [ 1974.506143] EXT4-fs (nbd0): unable to read superblock > [ 1974.507386] EXT4-fs (nbd0): unable to read superblock > [ 1974.508735] EXT4-fs (nbd0): unable to read superblock > [ 1974.510034] EXT4-fs (nbd0): unable to read superblock > [ 1974.511149] EXT4-fs (nbd0): unable to read superblock > [ 1974.512369] EXT4-fs (nbd0): unable to read superblock > [ 1974.513666] EXT4-fs (nbd0): unable to read superblock > [ 1974.514934] EXT4-fs (nbd0): unable to read superblock > [ 1974.516180] EXT4-fs (nbd0): unable to read superblock > [ 1974.517522] EXT4-fs (nbd0): unable to read superblock > [ 1974.518802] EXT4-fs (nbd0): unable to read superblock > [ 1974.519970] EXT4-fs (nbd0): unable to read superblock > [ 1974.521141] EXT4-fs (nbd0): unable to read superblock > [ 1974.522234] EXT4-fs (nbd0): unable to read superblock > [ 1974.523580] EXT4-fs (nbd0): unable to read superblock > [ 1974.524815] EXT4-fs (nbd0): unable to read superblock > [ 1974.526017] EXT4-fs (nbd0): unable to read superblock > [ 1974.527196] EXT4-fs (nbd0): unable to read superblock > [ 1974.528593] EXT4-fs (nbd0): unable to read superblock > [ 1974.529885] EXT4-fs (nbd0): unable to read superblock > [ [ 1975.031424] EXT4-fs (nbd0): unable to read superblock > [ 1975.032782] EXT4-fs (nbd0): unable to read superblock > [ 1975.034091] EXT4-fs (nbd0): unable to read superblock > [ 1975.035352] EXT4-fs (nbd0): unable to read superblock > [ 1975.036692] EXT4-fs (nbd0): unable to read superblock > [ 1975.037991] EXT4-fs (nbd0): unable to read superblock > [ 1975.039322] EXT4-fs (nbd0): unable to read superblock > [ 1975.040565] EXT4-fs (nbd0): unable to read superblock > [ 1975.041701] EXT4-fs (nbd0): unable to read superblock > [ 1975.042957] EXT4-fs (nbd0): unable to read superblock > [ 1975.044086] EXT4-fs (nbd0): unable to read superblock > [ 1975.045396] EXT4-fs (nbd0): unable to read superblock > [ 1975.046711] EXT4-fs (nbd0): unable to read superblock > [ 1975.047956] EXT4-fs (nbd0): unable to read superblock > [ 1975.048935] EXT4-fs (nbd0): unable to read superblock > [ 1975.050139] EXT4-fs (nbd0): unable to read superblock > [ 1975.051296] EXT4-fs (nbd0): unable to read superblock > [ 1975.052417] EXT4-fs (nbd0): unable to read superblock > [ 1975.053654] EXT4-fs (nbd0): unable to read superblock > [ 1975.054968] EXT4-fs (nbd0): unable to read superblock > [ 1975.08[ 1975.531562] bio_check_eod: 215 callbacks suppressed > [ 1975.531566] mount_clear_soc: attempt to access beyond end of device > [ 1975.531566] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1975.557154] EXT4-fs (nbd0): unable to read superblock > [ 1975.558576] mount_clear_soc: attempt to access beyond end of device > [ 1975.558576] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1975.559633] EXT4-fs (nbd0): unable to read superblock > [ 1975.560951] mount_clear_soc: attempt to access beyond end of device > [ 1975.560951] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1975.561954] EXT4-fs (nbd0): unable to read superblock > [ 1975.563104] mount_clear_soc: attempt to access beyond end of device > [ 1975.563104] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1975.564184] EXT4-fs (nbd0): unable to read superblock > [ 1975.565473] mount_clear_soc: attempt to access beyond end of device > [ 1975.565473] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1975.566587] EXT4-fs (nbd0): unable to read superblock > [ 1975.567951] mount_clear_soc: attempt to access beyond end of device > [ 1975.567951] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1975.569011] EXT4-fs (nbd0): unable to read superblock > [ 1975.570196] mount_clear_soc: attempt to access beyond end of device > [ 1975.570196] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ s beyond end of device > [ 1975.771395] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1975.965355] BUG: kernel NULL pointer dereference, address: 0000000000000000 > [ 1975.965358] #PF: supervisor instruction fetch in kernel mode > [ 1975.965360] #PF: error_code(0x0010) - not-present page > [ 1975.965362] PGD 0 P4D 0 > [ 1975.965365] Oops: 0010 [#1] PREEMPT SMP PTI > [ 1975.965369] CPU: 26 PID: 0 Comm: swapper/26 Tainted: G W I > 6.8.0 #1 > [ 1975.965373] Hardware name: HP ProLiant DL360e Gen8, BIOS P73 05/24/2019 > [ 1975.965375] RIP: 0010:0x0 > [ 1976.072029] EXT4-fs (nbd0): unable to read superblock > [ 1976.072297] Code: Unable to access opcode bytes at 0xffffffffffffffd6. > [ 1976.073790] mount_clear_soc: attempt to access beyond end of device > [ 1976.073790] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1976.074355] RSP: 0018:ffffb79741fc0eb8 EFLAGS: 00010282 > [ 1976.074709] EXT4-fs (nbd0): unable to read superblock > [ 1976.074822] > [ 1976.075594] mount_clear_soc: attempt to access beyond end of device > [ 1976.075594] nbd0: rw=4096, sector=2, nr_sectors = 2 limit=0 > [ 1976.076338] RAX: 0000000000000001 RBX: 0000000000000003 RCX: 0000000000000000 > [ 1976.076624] EXT4-fs (nbd0): unable to read superblock > [ 1976.076870] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff94d18d952ce8 > [ 1976.077974] EXT4-fs (nbd0): unable to read superblock > [ 1976.078348] RBP: ffff94d2[ 1976.080108] R13: ffffb79741fc0ef0 R14: > 0000000000000002 R15: 0000000000000000 > [ 1976.080111] FS: 0000000000000000(0000) GS:ffff94d4b7900000(0000) > knlGS:0000000000000000 > [ 1976.080983] EXT4-fs (nbd0): unable to read superblock > [ 1976.247337] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > [ 1976.247340] CR2: ffffffffffffffd6 CR3: 00000000b8422003 CR4: 00000000000606f0 > [ 1976.247343] Call Trace: > [ 1976.247345] <IRQ> > [ 1976.247346] ? __die+0x23/0x70 > [ 1976.247353] ? page_fault_oops+0x170/0x580 > [ 1976.247357] ? exc_page_fault+0x7e/0x180 > [ 1976.247363] ? asm_exc_page_fault+0x26/0x30 > [ 1976.247371] rcu_do_batch+0x1c6/0x560 > [ 1976.441610] EXT4-fs (nbd0): unable to read superblock > [ 1976.578818] ? rcu_do_batch+0x165/0x560 > [ 1976.578823] rcu_core+0x1b2/0x4b0 > [ 1976.578827] __do_softirq+0xd9/0x2c5 > [ 1976.578833] __irq_exit_rcu+0x95/0xb0 > [ 1976.582102] EXT4-fs (nbd0): unable to read superblock > [ 1976.582138] sysvec_apic_timer_interrupt+0x71/0x90 > [ 1976.583407] EXT4-fs (nbd0): unable to read superblock > [ 1976.583567] </IRQ> > [ 1976.583569] <TASK> > [ 1976.583570] asm_sysvec_apic_timer_interrupt+0x1a/0x20 > [ 1976.583575] RIP: 0010:cpuidle_enter_state+0xc6/0x420 > [ 1976.583578] Code: 00 00 e8 8d f5 13 ff e[ 1976.584827] RSP: > 0018:ffffb7974123fe98 EFLAGS: 00000246 > [ 1976.584830] RAX: ffff94d4b7900000 RBX: 0000000000000004 RCX: 0000000000000000 > [ 1976.584832] RDX: 000001cbfcef036a RSI: fffffe40b5d57332 RDI: 0000000000000000 > [ 1976.584833] RBP: ffff94d4b7941108 R08: 0000000000000002 R09: 0000000000000369 > [ 1976.584835] R10: 0000000000000018 R11: ffff94d4b79343e4 R12: ffffffffb7647220 > [ 1976.584837] R13: 000001cbfcef036a R14: 0000000000000004 R15: 0000000000000000 > [ 1976.584840] ? cpuidle_enter_state+0xb7/0x420 > [ 1976.584843] cpuidle_enter+0x2d/0x40 > [ 1976.585710] EXT4-fs (nbd0): unable to read superblock > [ 1976.585811] do_idle+0x1e5/0x240 > [ 1976.586621] EXT4-fs (nbd0): unable to read superblock > [ 1976.586825] cpu_startup_entry+0x28/0x30 > [ 1976.587568] EXT4-fs (nbd0): unable to read superblock > [ 1976.588147] start_secondary+0x11c/0x140 > [ 1976.588992] EXT4-fs (nbd0): unable to read superblock > [ 1976.589410] common_startup_64+0x13e/0x141 > [ 1976.590267] EXT4-fs (nbd0): unable to read superblock > [ 1976.956881] </TASK> > [ 1976.956882] Modules linked in: nbd nvme_keyring nvme_core nvme_auth > pktcdvd rfkill intel_rapl_msr intel_rapl_common sb_edac > x86_pkg_temp_thermal intel_powerclamp coretemp sunrpc kvm_intel > ipmi_ssif kvm rapl intel_cstate > [ 1[ 1977.094336] EXT4-fs (nbd0): unable to read superblock > [ 1977.094740] ipmi_si intel_pmc_bxt hpilo ipmi_devintf igb pcspkr > acpi_power_meter iTCO_vendor_support ioatdma lpc_ich ipmi_msghandler > dca fuse loop nfnetlink zram xfs crct10dif_pclmul crc32c_intel > polyval_clmulni polyval_generic ghash_clmulni_intel sha512_ssse3 > sha256_ssse3 sha1_ssse3 serio_raw mgag200 i2c_algo_bit hpwdt > [ 1977.095963] EXT4-fs (nbd0): unable to read superblock > [ 1977.096494] [last unloaded: crc32_pclmul] > [ 1977.097365] EXT4-fs (nbd0): unable to read superblock > [ 1977.097489] > [ 1977.097492] CR2: 0000000000000000 > [ 1977.098348] EXT4-fs (nbd0): unable to read superblock > [ 1977.098402] ---[ end trace 0000000000000000 ]--- > [ 1977.129544] EXT4-fs (nbd0): unable to read superblock > [ 1977.271906] ERST: [Firmware Warn]: Firmware does not respond in time. > [ 1977.348338] EXT4-fs (nbd0): unable to read superblock > [ 1977.491887] ERST: [Firmware Warn]: Firmware does not respond in time. > [ 1977.594276] EXT4-fs (nbd0): unable to read superblock > [ 1977.603176] ERST: [Firmware Warn]: Firmware does not respond in time. > [ 1977.604077] EXT4-fs (nbd0): unable to read superblock > [ 1977.607491] ERST: [Firmware Warn]: Firmware does not respond in time. > [ 1977.607773] EXT4-fs (nbd0): unable to read superblock > [ 1977.609318] EXT4-fs (nbd0):[ 1977.864344] Code: Unable to access > opcode bytes at 0xffffffffffffffd6. > [ 1977.864345] RSP: 0018:ffffb79741fc0eb8 EFLAGS: 00010282 > [ 1977.864348] RAX: 0000000000000001 RBX: 0000000000000003 RCX: 0000000000000000 > [ 1977.864349] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff94d18d952ce8 > [ 1977.864351] RBP: ffff94d2c0f95180 R08: 00000000000008f7 R09: 000000000000001a > [ 1977.864353] R10: 0000000062616c73 R11: 00000000616c7320 R12: ffff94d4b7937080 > [ 1977.864355] R13: ffffb79741fc0ef0 R14: 0000000000000002 R15: 0000000000000000 > [ 1977.864357] FS: 0000000000000000(0000) GS:ffff94d4b7900000(0000) > knlGS:0000000000000000 > [ 1977.864359] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > [ 1977.864360] CR2: ffffffffffffffd6 CR3: 00000000b8422003 CR4: 00000000000606f0 > [ 1977.864363] Kernel panic - not syncing: Fatal exception in interrupt > [ 1977.864426] Kernel Offset: 0x34000000 from 0xffffffff81000000 > (relocation range: 0xffffffff80000000-0xffffffffbfffffff) > [ 1978.116728] ---[ end Kernel panic - not syncing: Fatal exception in > interrupt ]--- > > > -- > Best Regards, > Yi Zhang -- Best Regards, Yi Zhang
On 3/18/24 09:38, Yu Kuai wrote: > Hi, > > 在 2024/03/18 17:19, Jan Kara 写道: >> On Thu 22-02-24 20:45:53, Yu Kuai wrote: >>> From: Yu Kuai <yukuai3@huawei.com> >>> >>> Now that dm upper layer already statsh the file of opened device in >>> 'dm_dev->bdev_file', it's ok to get inode from the file. >>> >>> Signed-off-by: Yu Kuai <yukuai3@huawei.com> >> >> Given there are like three real uses of ->bdev in dm-vdo, I suspect it >> might be better to just replace bdev with bdev_file in struct io_factory >> and in struct uds_parameters. > > Yes, this make sense. > > Thanks for the review! > Kuai > At a glance this looks completely reasonable to me. However, can you be sure to CC: dm-devel@lists.linux.dev for dm-vdo patches? I almost missed seeing this patch. I will try to give it a proper review tomorrow. Matt >> >> Honza >> >>> --- >>> drivers/md/dm-vdo/dedupe.c | 3 ++- >>> drivers/md/dm-vdo/dm-vdo-target.c | 5 +++-- >>> drivers/md/dm-vdo/indexer/config.c | 1 + >>> drivers/md/dm-vdo/indexer/config.h | 3 +++ >>> drivers/md/dm-vdo/indexer/index-layout.c | 6 +++--- >>> drivers/md/dm-vdo/indexer/index-layout.h | 2 +- >>> drivers/md/dm-vdo/indexer/index-session.c | 13 +++++++------ >>> drivers/md/dm-vdo/indexer/index.c | 4 ++-- >>> drivers/md/dm-vdo/indexer/index.h | 2 +- >>> drivers/md/dm-vdo/indexer/indexer.h | 4 +++- >>> drivers/md/dm-vdo/indexer/io-factory.c | 13 ++++++++----- >>> drivers/md/dm-vdo/indexer/io-factory.h | 4 ++-- >>> drivers/md/dm-vdo/indexer/volume.c | 4 ++-- >>> drivers/md/dm-vdo/indexer/volume.h | 2 +- >>> 14 files changed, 39 insertions(+), 27 deletions(-) >>> >>> diff --git a/drivers/md/dm-vdo/dedupe.c b/drivers/md/dm-vdo/dedupe.c >>> index a9b189395592..532294a15174 100644 >>> --- a/drivers/md/dm-vdo/dedupe.c >>> +++ b/drivers/md/dm-vdo/dedupe.c >>> @@ -2592,7 +2592,8 @@ static void resume_index(void *context, struct >>> vdo_completion *parent) >>> int result; >>> zones->parameters.bdev = config->owned_device->bdev; >>> - result = uds_resume_index_session(zones->index_session, >>> zones->parameters.bdev); >>> + zones->parameters.bdev_file = config->owned_device->bdev_file; >>> + result = uds_resume_index_session(zones->index_session, >>> zones->parameters.bdev_file); >>> if (result != UDS_SUCCESS) >>> vdo_log_error_strerror(result, "Error resuming dedupe index"); >>> diff --git a/drivers/md/dm-vdo/dm-vdo-target.c >>> b/drivers/md/dm-vdo/dm-vdo-target.c >>> index 89d00be9f075..b2d7f68e70be 100644 >>> --- a/drivers/md/dm-vdo/dm-vdo-target.c >>> +++ b/drivers/md/dm-vdo/dm-vdo-target.c >>> @@ -883,7 +883,7 @@ static int parse_device_config(int argc, char >>> **argv, struct dm_target *ti, >>> } >>> if (config->version == 0) { >>> - u64 device_size = >>> i_size_read(config->owned_device->bdev->bd_inode); >>> + u64 device_size = >>> i_size_read(file_inode(config->owned_device->bdev_file)); >>> config->physical_blocks = device_size / VDO_BLOCK_SIZE; >>> } >>> @@ -1018,7 +1018,8 @@ static void vdo_status(struct dm_target *ti, >>> status_type_t status_type, >>> static block_count_t __must_check >>> get_underlying_device_block_count(const struct vdo *vdo) >>> { >>> - return i_size_read(vdo_get_backing_device(vdo)->bd_inode) / >>> VDO_BLOCK_SIZE; >>> + return >>> i_size_read(file_inode(vdo->device_config->owned_device->bdev_file)) / >>> + VDO_BLOCK_SIZE; >>> } >>> static int __must_check process_vdo_message_locked(struct vdo *vdo, >>> unsigned int argc, >>> diff --git a/drivers/md/dm-vdo/indexer/config.c >>> b/drivers/md/dm-vdo/indexer/config.c >>> index 260993ce1944..f1f66e232b54 100644 >>> --- a/drivers/md/dm-vdo/indexer/config.c >>> +++ b/drivers/md/dm-vdo/indexer/config.c >>> @@ -347,6 +347,7 @@ int uds_make_configuration(const struct >>> uds_parameters *params, >>> config->sparse_sample_rate = (params->sparse ? >>> DEFAULT_SPARSE_SAMPLE_RATE : 0); >>> config->nonce = params->nonce; >>> config->bdev = params->bdev; >>> + config->bdev_file = params->bdev_file; >>> config->offset = params->offset; >>> config->size = params->size; >>> diff --git a/drivers/md/dm-vdo/indexer/config.h >>> b/drivers/md/dm-vdo/indexer/config.h >>> index fe7958263ed6..688f7450183e 100644 >>> --- a/drivers/md/dm-vdo/indexer/config.h >>> +++ b/drivers/md/dm-vdo/indexer/config.h >>> @@ -28,6 +28,9 @@ struct uds_configuration { >>> /* Storage device for the index */ >>> struct block_device *bdev; >>> + /* Opened device fot the index */ >>> + struct file *bdev_file; >>> + >>> /* The maximum allowable size of the index */ >>> size_t size; >>> diff --git a/drivers/md/dm-vdo/indexer/index-layout.c >>> b/drivers/md/dm-vdo/indexer/index-layout.c >>> index 1453fddaa656..6dd80a432fe5 100644 >>> --- a/drivers/md/dm-vdo/indexer/index-layout.c >>> +++ b/drivers/md/dm-vdo/indexer/index-layout.c >>> @@ -1672,7 +1672,7 @@ static int create_layout_factory(struct >>> index_layout *layout, >>> size_t writable_size; >>> struct io_factory *factory = NULL; >>> - result = uds_make_io_factory(config->bdev, &factory); >>> + result = uds_make_io_factory(config->bdev_file, &factory); >>> if (result != UDS_SUCCESS) >>> return result; >>> @@ -1745,9 +1745,9 @@ void vdo_free_index_layout(struct index_layout >>> *layout) >>> } >>> int uds_replace_index_layout_storage(struct index_layout *layout, >>> - struct block_device *bdev) >>> + struct file *bdev_file) >>> { >>> - return uds_replace_storage(layout->factory, bdev); >>> + return uds_replace_storage(layout->factory, bdev_file); >>> } >>> /* Obtain a dm_bufio_client for the volume region. */ >>> diff --git a/drivers/md/dm-vdo/indexer/index-layout.h >>> b/drivers/md/dm-vdo/indexer/index-layout.h >>> index bd9b90c84a70..9b0c850fe9a7 100644 >>> --- a/drivers/md/dm-vdo/indexer/index-layout.h >>> +++ b/drivers/md/dm-vdo/indexer/index-layout.h >>> @@ -24,7 +24,7 @@ int __must_check uds_make_index_layout(struct >>> uds_configuration *config, bool ne >>> void vdo_free_index_layout(struct index_layout *layout); >>> int __must_check uds_replace_index_layout_storage(struct >>> index_layout *layout, >>> - struct block_device *bdev); >>> + struct file *bdev_file); >>> int __must_check uds_load_index_state(struct index_layout *layout, >>> struct uds_index *index); >>> diff --git a/drivers/md/dm-vdo/indexer/index-session.c >>> b/drivers/md/dm-vdo/indexer/index-session.c >>> index 1949a2598656..df8f8122a22d 100644 >>> --- a/drivers/md/dm-vdo/indexer/index-session.c >>> +++ b/drivers/md/dm-vdo/indexer/index-session.c >>> @@ -460,15 +460,16 @@ int uds_suspend_index_session(struct >>> uds_index_session *session, bool save) >>> return uds_status_to_errno(result); >>> } >>> -static int replace_device(struct uds_index_session *session, struct >>> block_device *bdev) >>> +static int replace_device(struct uds_index_session *session, struct >>> file *bdev_file) >>> { >>> int result; >>> - result = uds_replace_index_storage(session->index, bdev); >>> + result = uds_replace_index_storage(session->index, bdev_file); >>> if (result != UDS_SUCCESS) >>> return result; >>> - session->parameters.bdev = bdev; >>> + session->parameters.bdev = file_bdev(bdev_file); >>> + session->parameters.bdev_file = bdev_file; >>> return UDS_SUCCESS; >>> } >>> @@ -477,7 +478,7 @@ static int replace_device(struct >>> uds_index_session *session, struct block_device >>> * device differs from the current backing store, the index will >>> start using the new backing store. >>> */ >>> int uds_resume_index_session(struct uds_index_session *session, >>> - struct block_device *bdev) >>> + struct file *bdev_file) >>> { >>> int result = UDS_SUCCESS; >>> bool no_work = false; >>> @@ -502,8 +503,8 @@ int uds_resume_index_session(struct >>> uds_index_session *session, >>> if (no_work) >>> return result; >>> - if ((session->index != NULL) && (bdev != >>> session->parameters.bdev)) { >>> - result = replace_device(session, bdev); >>> + if ((session->index != NULL) && (bdev_file != >>> session->parameters.bdev_file)) { >>> + result = replace_device(session, bdev_file); >>> if (result != UDS_SUCCESS) { >>> mutex_lock(&session->request_mutex); >>> session->state &= ~IS_FLAG_WAITING; >>> diff --git a/drivers/md/dm-vdo/indexer/index.c >>> b/drivers/md/dm-vdo/indexer/index.c >>> index bd2405738c50..3600a169ca98 100644 >>> --- a/drivers/md/dm-vdo/indexer/index.c >>> +++ b/drivers/md/dm-vdo/indexer/index.c >>> @@ -1334,9 +1334,9 @@ int uds_save_index(struct uds_index *index) >>> return result; >>> } >>> -int uds_replace_index_storage(struct uds_index *index, struct >>> block_device *bdev) >>> +int uds_replace_index_storage(struct uds_index *index, struct file >>> *bdev_file) >>> { >>> - return uds_replace_volume_storage(index->volume, index->layout, >>> bdev); >>> + return uds_replace_volume_storage(index->volume, index->layout, >>> bdev_file); >>> } >>> /* Accessing statistics should be safe from any thread. */ >>> diff --git a/drivers/md/dm-vdo/indexer/index.h >>> b/drivers/md/dm-vdo/indexer/index.h >>> index 7fbc63db4131..9428ee025cda 100644 >>> --- a/drivers/md/dm-vdo/indexer/index.h >>> +++ b/drivers/md/dm-vdo/indexer/index.h >>> @@ -72,7 +72,7 @@ int __must_check uds_save_index(struct uds_index >>> *index); >>> void vdo_free_index(struct uds_index *index); >>> int __must_check uds_replace_index_storage(struct uds_index *index, >>> - struct block_device *bdev); >>> + struct file *bdev_file); >>> void uds_get_index_stats(struct uds_index *index, struct >>> uds_index_stats *counters); >>> diff --git a/drivers/md/dm-vdo/indexer/indexer.h >>> b/drivers/md/dm-vdo/indexer/indexer.h >>> index a832a34d9436..5dd2c93f12c2 100644 >>> --- a/drivers/md/dm-vdo/indexer/indexer.h >>> +++ b/drivers/md/dm-vdo/indexer/indexer.h >>> @@ -130,6 +130,8 @@ struct uds_volume_record { >>> struct uds_parameters { >>> /* The block_device used for storage */ >>> struct block_device *bdev; >>> + /* Then opened block_device */ >>> + struct file *bdev_file; >>> /* The maximum allowable size of the index on storage */ >>> size_t size; >>> /* The offset where the index should start */ >>> @@ -314,7 +316,7 @@ int __must_check uds_suspend_index_session(struct >>> uds_index_session *session, bo >>> * start using the new backing store instead. >>> */ >>> int __must_check uds_resume_index_session(struct uds_index_session >>> *session, >>> - struct block_device *bdev); >>> + struct file *bdev_file); >>> /* Wait until all outstanding index operations are complete. */ >>> int __must_check uds_flush_index_session(struct uds_index_session >>> *session); >>> diff --git a/drivers/md/dm-vdo/indexer/io-factory.c >>> b/drivers/md/dm-vdo/indexer/io-factory.c >>> index 61104d5ccd61..a855c3ac73bc 100644 >>> --- a/drivers/md/dm-vdo/indexer/io-factory.c >>> +++ b/drivers/md/dm-vdo/indexer/io-factory.c >>> @@ -23,6 +23,7 @@ >>> */ >>> struct io_factory { >>> struct block_device *bdev; >>> + struct file *bdev_file; >>> atomic_t ref_count; >>> }; >>> @@ -59,7 +60,7 @@ static void uds_get_io_factory(struct io_factory >>> *factory) >>> atomic_inc(&factory->ref_count); >>> } >>> -int uds_make_io_factory(struct block_device *bdev, struct io_factory >>> **factory_ptr) >>> +int uds_make_io_factory(struct file *bdev_file, struct io_factory >>> **factory_ptr) >>> { >>> int result; >>> struct io_factory *factory; >>> @@ -68,16 +69,18 @@ int uds_make_io_factory(struct block_device >>> *bdev, struct io_factory **factory_p >>> if (result != VDO_SUCCESS) >>> return result; >>> - factory->bdev = bdev; >>> + factory->bdev = file_bdev(bdev_file); >>> + factory->bdev_file = bdev_file; >>> atomic_set_release(&factory->ref_count, 1); >>> *factory_ptr = factory; >>> return UDS_SUCCESS; >>> } >>> -int uds_replace_storage(struct io_factory *factory, struct >>> block_device *bdev) >>> +int uds_replace_storage(struct io_factory *factory, struct file >>> *bdev_file) >>> { >>> - factory->bdev = bdev; >>> + factory->bdev = file_bdev(bdev_file); >>> + factory->bdev_file = bdev_file; >>> return UDS_SUCCESS; >>> } >>> @@ -90,7 +93,7 @@ void uds_put_io_factory(struct io_factory *factory) >>> size_t uds_get_writable_size(struct io_factory *factory) >>> { >>> - return i_size_read(factory->bdev->bd_inode); >>> + return i_size_read(file_inode(factory->bdev_file)); >>> } >>> /* Create a struct dm_bufio_client for an index region starting at >>> offset. */ >>> diff --git a/drivers/md/dm-vdo/indexer/io-factory.h >>> b/drivers/md/dm-vdo/indexer/io-factory.h >>> index 60749a9ff756..e5100ab57754 100644 >>> --- a/drivers/md/dm-vdo/indexer/io-factory.h >>> +++ b/drivers/md/dm-vdo/indexer/io-factory.h >>> @@ -24,11 +24,11 @@ enum { >>> SECTORS_PER_BLOCK = UDS_BLOCK_SIZE >> SECTOR_SHIFT, >>> }; >>> -int __must_check uds_make_io_factory(struct block_device *bdev, >>> +int __must_check uds_make_io_factory(struct file *bdev_file, >>> struct io_factory **factory_ptr); >>> int __must_check uds_replace_storage(struct io_factory *factory, >>> - struct block_device *bdev); >>> + struct file *bdev_file); >>> void uds_put_io_factory(struct io_factory *factory); >>> diff --git a/drivers/md/dm-vdo/indexer/volume.c >>> b/drivers/md/dm-vdo/indexer/volume.c >>> index 8b21ec93f3bc..a292840a83e3 100644 >>> --- a/drivers/md/dm-vdo/indexer/volume.c >>> +++ b/drivers/md/dm-vdo/indexer/volume.c >>> @@ -1467,12 +1467,12 @@ int uds_find_volume_chapter_boundaries(struct >>> volume *volume, u64 *lowest_vcn, >>> int __must_check uds_replace_volume_storage(struct volume *volume, >>> struct index_layout *layout, >>> - struct block_device *bdev) >>> + struct file *bdev_file) >>> { >>> int result; >>> u32 i; >>> - result = uds_replace_index_layout_storage(layout, bdev); >>> + result = uds_replace_index_layout_storage(layout, bdev_file); >>> if (result != UDS_SUCCESS) >>> return result; >>> diff --git a/drivers/md/dm-vdo/indexer/volume.h >>> b/drivers/md/dm-vdo/indexer/volume.h >>> index 7fdd44464db2..5861654d837e 100644 >>> --- a/drivers/md/dm-vdo/indexer/volume.h >>> +++ b/drivers/md/dm-vdo/indexer/volume.h >>> @@ -131,7 +131,7 @@ void vdo_free_volume(struct volume *volume); >>> int __must_check uds_replace_volume_storage(struct volume *volume, >>> struct index_layout *layout, >>> - struct block_device *bdev); >>> + struct file *bdev_file); >>> int __must_check uds_find_volume_chapter_boundaries(struct volume >>> *volume, >>> u64 *lowest_vcn, u64 *highest_vcn, >>> -- >>> 2.39.2 >>> > >
Hi, 在 2024/03/19 9:18, Yu Kuai 写道: > Hi, > > 在 2024/03/18 17:39, Christian Brauner 写道: >> On Sat, Mar 16, 2024 at 10:49:33AM +0800, Yu Kuai wrote: >>> Hi, Christian >>> >>> 在 2024/03/15 21:54, Christian Brauner 写道: >>>> On Fri, Mar 15, 2024 at 08:08:49PM +0800, Yu Kuai wrote: >>>>> Hi, Christian >>>>> Hi, Christoph >>>>> Hi, Jan >>>>> >>>>> Perhaps now is a good time to send a formal version of this set. >>>>> However, I'm not sure yet what branch should I rebase and send this >>>>> set. >>>>> Should I send to the vfs tree? >>>> >>>> Nearly all of it is in fs/ so I'd say yes. >>>> . >>> >>> I see that you just create a new branch vfs.fixes, perhaps can I rebase >>> this set against this branch? >> >> Please base it on vfs.super. I'll rebase it to v6.9-rc1 on Sunday. > > Okay, I just see that vfs.super doesn't contain commit > 1cdeac6da33f("btrfs: pass btrfs_device to btrfs_scratch_superblocks()"), > and you might need to fix the conflict at some point. And there is another problem, dm-vdo doesn't exist in vfs.super yet. Do you still want me to rebase here? Thanks, Kuai > > Thanks, > Kuai > >> . >> > > . >
On Mon, Mar 18, 2024 at 10:00:22PM +0000, Pavel Begunkov wrote:
> Mandate ctx locking for task_work. Then, remove aux CQE caches mostly
> used by multishot requests and post them directly into the CQ.
>
> It's leaving some of the pre existing issue_flags and state conversion
> non conformant chunks, which will need to clean up later.
>
> v3: pass IO_URING_F_COMPLETE_DEFER to the cmd cancellation path
> drop patch moving request cancellation list removal to tw
> drop all other ublk changes
For the series, pass ublksrv test.
Tested-by: Ming Lei <ming.lei@redhat.com>
Thanks,
Ming
duplicated code in redo_fd_request(), unlock_fdc() function has the same code "do_floppy = NULL" inside. Signed-off-by: Yufeng Wang <wangyufeng@kylinos.cn> Suggested-by: Denis Efremov <efremov@linux.com> --- v2: The commit title is too long, update a new short commit title. --- drivers/block/floppy.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/block/floppy.c b/drivers/block/floppy.c index 1b399ec8c07d..25c9d85667f1 100644 --- a/drivers/block/floppy.c +++ b/drivers/block/floppy.c @@ -2787,7 +2787,6 @@ static void redo_fd_request(void) pending = set_next_request(); spin_unlock_irq(&floppy_lock); if (!pending) { - do_floppy = NULL; unlock_fdc(); return; } -- 2.34.1
On Mon, Mar 18, 2024 at 10:00:27PM +0000, Pavel Begunkov wrote:
> uring_cmd implementations should not try to guess issue_flags, use a
> freshly added helper io_uring_cmd_complete() instead.
>
> Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>
> Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
Reviewed-by: Ming Lei <ming.lei@redhat.com>
Thanks,
Ming
On Mon, Mar 18, 2024 at 10:00:26PM +0000, Pavel Begunkov wrote:
> io_uring_cmd_complete() does exactly what io_uring_cmd_done() does, that
> is completing the request, but doesn't ask for issue_flags argument. We
> have a couple of users hardcoding some random issue_flags values in
> drivers, which they absolutely should not do. This function will be used
> to get rid of them. Also, add comments warning users that they're only
> allowed to pass issue_flags that were given from io_uring.
>
> Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
Reviewed-by: Ming Lei <ming.lei@redhat.com>
Thanks
Ming
On Mon, Mar 18, 2024 at 10:00:25PM +0000, Pavel Begunkov wrote:
> !IO_URING_F_UNLOCKED does not translate to availability of the deferred
> completion infra, IO_URING_F_COMPLETE_DEFER does, that what we should
> pass and look for to use io_req_complete_defer() and other variants.
>
> Luckily, it's not a real problem as two wrongs actually made it right,
> at least as far as io_uring_cmd_work() goes.
>
> Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
Reviewed-by: Ming Lei <ming.lei@redhat.com>
Thanks
Ming
Hi, 在 2024/03/18 17:39, Christian Brauner 写道: > On Sat, Mar 16, 2024 at 10:49:33AM +0800, Yu Kuai wrote: >> Hi, Christian >> >> 在 2024/03/15 21:54, Christian Brauner 写道: >>> On Fri, Mar 15, 2024 at 08:08:49PM +0800, Yu Kuai wrote: >>>> Hi, Christian >>>> Hi, Christoph >>>> Hi, Jan >>>> >>>> Perhaps now is a good time to send a formal version of this set. >>>> However, I'm not sure yet what branch should I rebase and send this set. >>>> Should I send to the vfs tree? >>> >>> Nearly all of it is in fs/ so I'd say yes. >>> . >> >> I see that you just create a new branch vfs.fixes, perhaps can I rebase >> this set against this branch? > > Please base it on vfs.super. I'll rebase it to v6.9-rc1 on Sunday. Okay, I just see that vfs.super doesn't contain commit 1cdeac6da33f("btrfs: pass btrfs_device to btrfs_scratch_superblocks()"), and you might need to fix the conflict at some point. Thanks, Kuai > . >
On Mon, Mar 18, 2024 at 10:00:24PM +0000, Pavel Begunkov wrote:
> io_uring cmd converts struct io_tw_state to issue_flags and later back
> to io_tw_state, it's awfully ill-fated, not to mention that intermediate
> issue_flags state is not correct.
>
> Get rid of the last conversion, drag through tw everything that came
> with IO_URING_F_UNLOCKED, and replace io_req_complete_defer() with a
> direct call to io_req_complete_defer(), at least for the time being.
>
> Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
Reviewed-by: Ming Lei <ming.lei@redhat.com>
Thanks,
Ming
On Mon, Mar 18, 2024 at 10:00:23PM +0000, Pavel Begunkov wrote:
> io_uring_try_cancel_uring_cmd() is a part of the cmd handling so let's
> move it closer to all cmd bits into uring_cmd.c
>
> Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
Reviewed-by: Ming Lei <ming.lei@redhat.com>
Thanks
Ming
On 3/18/24 16:54, Guenter Roeck wrote:
> On 3/18/24 13:37, Kenneth Raeburn wrote:
>> (resend because of accidental HTML lossage)
>>
>> On Thu, Mar 14, 2024 at 7:38 PM Guenter Roeck <linux@roeck-us.net> wrote:
>>> On sparc64, with gcc 11.4, the above code results in:
>>>
>>> ERROR: modpost: "__bswapdi2" [drivers/md/dm-vdo/dm-vdo.ko] undefined!
>>>
>>> Guenter
>>
>> Thanks for catching that. I don't think our team has any sparc
>> machines readily available for testing.
>> This is an artifact of our having imported user-mode code to use in
>> the kernel. We should probably be using le64_to_cpup and friends, as
>> we do elsewhere, so it doesn't try to pull in libgcc support routines.
>>
>
> I am kind of getting wary about reporting such issues. Should I drop
> building dm-vdo images for sparc ? Would it be possible to add
> "depends on BROKEN if SPARC" configuration option to indicate that
> the code isn't expected to be buildable on sparc, much less work ?
First off, sorry for the slow response. I was away for the last couple
of days.
I would encourage you to report issues when you find them.
Theoretically, VDO should work on sparc. However since we don't have
that architecture readily available to us, we won't know what to fix
unless it gets reported.
In this case, we really shouldn't be relying on these libgcc builtins
anyway. I hope to have a patch in a couple of days that you can try out.
If it turns out there are more extensive issues with VDO on sparc, I am
open to disabling the config, but I hope it won't come to that.
Matt
On Mon, Mar 18, 2024 at 11:29:17AM +0100, Christian Brauner wrote:
> Don't forget:
>
> mknod /my/xfs/file/system b 8 0
>
> which means you're not opening it via devtmpfs but via xfs. IOW, the
> inode for that file is from xfs.
Yes. file_inode() for block devices is always the "upper" fs, which can
be any file system supporting device nodes. file->f_mapping->host will
always be the bdevfs inode, and nothing in the I/O path should ever be
using file_inode().
On Mon, Mar 18, 2024 at 03:19:03PM +0800, Yu Kuai wrote:
> I come up with an ideal:
>
> While opening the block_device the first time, store the generated new
> file in "bd_inode->i_private". And release it after the last opener
> close the block_device.
>
> The advantages are:
> - multiple openers can share the same bdev_file;
> - raw block device ops can use the bdev_file as well, and there is no
> need to distinguish iomap/buffer_head for raw block_device;
>
> Please let me know what do you think?
That does sound very reasonable to me.
On Mon, Mar 18, 2024 at 10:26:23AM +0530, Nilay Shroff wrote:
> I have just tested the above patch and it's working well as expected.
> Now I don't see any issue formatting NVMe disk with the block-size of 512.
> I think we should commit the above changes.
Unfortunately I think it's going to break splitting the bios for real
multipath setups where the capabilities between the controllers are not
identical, i.e. another symptom of the problem of what limits we should
actually inherit.
I'll go backto the drawing board and will send out another patch.