New issue
Advanced search Search tips

Issue 903475 link

Starred by 1 user
Status: Assigned
Owner:
asavery@chromium.org
Cc:
evgreen@chromium.org
asavery@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocked on:
issue 903474


Sign in to add a comment

blktest reveals errors when using loopback over block device

Project Member Reported by gwendal@chromium.org, Nov 8 
chromoeos-install use loopback over block devices, but as pointed in https://lore.kernel.org/lkml/1541174532.196084.146.camel@acm.org/, this is not a supported configuration.

Using eve, blktests report issues that are not present when using a loopback over a file:

block/003 => loop6 (run various discard sizes)               [failed]
runtime       ...  0.335s
trim iops     ...  0
    --- tests/block/003.out     2018-11-08 11:28:55.000000000 -0800
    +++ /usr/local/blktests/results/loop6/block/003.out.bad     2018-11-08 11:58:14.951992141 -0800
    @@ -1,2 +1,5 @@
     Running block/003
    +discards: No I/O performed by psync, perhaps try --debug=io option for details?
    +fio exited with status 0   
    +4;fio-3.2;discards;0;5;0;0;0;0;0;0;0.000000;0.000000;0;0;0.000000;0.000000;1.000000%=0;5.000000%=0;10.000000%=0;20.000000%=0;30.000000%=0;40.000000%=0;50.000000%=0;60.000000%=0;70.000000%=0;80.000000%=0;90.000000%=0;95.0
00000%=0;99.000000%=0;99.500000%=0;99.900000%=0;99.950000%=0;99.990000%=0;0%=0;0%=0;0%=0;0;0;0.000000;0.000000;0;0;0.000000%;0.000000;0.000000;0;0;0;0;0;0;0.000000;0.000000;0;0;0.000000;0.000000;1.000000%=0;5.000000%=0;10.000
000%=0;20.000000%=0;30.000000%=0;40.000000%=0;50.000000%=0;60.000000%=0;70.000000%=0;80.000000%=0;90.000000%=0;95.000000%=0;99.000000%=0;99.500000%=0;99.900000%=0;99.950000%=0;99.990000%=0;0%=0;0%=0;0%=0;0;0;0.000000;0.000000
;0;0;0.000000%;0.000000;0.000000;0;0;0;0;0;0;0.000000;0.000000;0;0;0.000000;0.000000;1.000000%=0;5.000000%=0;10.000000%=0;20.000000%=0;30.000000%=0;40.000000%=0;50.000000%=0;60.000000%=0;70.000000%=0;80.000000%=0;90.000000%=0
;95.000000%=0;99.000000%=0;99.500000%=0;99.900000%=0;99.950000%=0;99.990000%=0;0%=0;0%=0;0%=0;0;0;0.000000;0.000000;0;0;0.000000%;0.000000;0.000000;0.000000%;0.000000%;1;0;12;100.0%;0.0%;0.0%;0.0%;0.0%;0.0%;0.0%;0.00%;0.00%;0
.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;0.00%;loop6;0;0;0;0;0;0;0;0.00%
     Test complete


block/013 => loop6 (try BLKRRPART on a mounted device)       [failed]
runtime     ...  0.841s
    --- tests/block/013.out     2018-11-08 11:28:55.000000000 -0800
    +++ /usr/local/blktests/results/loop6/block/013.out.bad     2018-11-08 11:58:22.578992112 -0800
    @@ -1,3 +1,3 @@
     Running block/013
    -Device or resource busy
    +blockdev: ioctl error on BLKRRPART: Invalid argument
     Test complete

Comment 1 by gwendal@chromium.org, Nov 8

Labels: OS-Chrome

Comment 2 by gwendal@chromium.org, Nov 28 

To repro:

- file based loop device:
 fallocate -l 10M /mnt/stateful_partition/unencrypted/cache/test_blktest
 losetup -f /mnt/stateful_partition/unencrypted/cache/test_blktest

- block based loop device:
 rootdev -s
/dev/nvme0n1p5
[Take the other root partition]:
 losetup -f /dev/nvme0n1p3

Create a config file:
 losetup -a               
...
/dev/loop7: [66305]:14286977 (/mnt/stateful_partition/unencrypted/cache/test_blktest)
/dev/loop8: [0006]:9606 (/dev/nvme0n1p3)

localhost /usr/local/blktests # echo "TEST_DEVS=(/dev/loop7 /dev/loop8)" > config
run test:
localhost /usr/local/blktests # ./check

Comment 3 by gwendal@chromium.org, Jan 8

Owner: asavery@chromium.org

Comment 4 by benhenry@google.com, Jan 11

Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Comment 5 by benhenry@google.com, Jan 11 

This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Comment 6 by asavery@chromium.org, Today (6 hours ago) 

I followed the repro steps with this change: https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/1428261 and saw the same results.
►

Sign in to add a comment