Closed Bad916 closed 1 year ago
Which system do you use? Can you attach the "ls /dev/loop" and "ls /dev/block/loop" output?
Which system do you use? Can you attach the "ls /dev/loop" and "ls /dev/block/loop" output?
1.We're using Android 13,linux kernel 5.10
2.ls: /dev/loop: /dev/loop-control
3.
But this is not a matter of stable recurrence,it’s occasionality matter
From the above log, /dev/block/loop40 exists and I guess it is not a symbolic link. It looks strange. Edward Liaw is planning to change ltp tst_device logic for loop device on android. He may know this failure's reason. @edliaw
There is a patchset trying to fix it: https://patchwork.ozlabs.org/project/ltp/list/?series=347760&state=*
Also, for AOSP it's better to use their fork https://android.googlesource.com/platform/external/ltp/ (noted at https://github.com/linux-test-project/ltp/wiki/Supported-kernel,-libc,-toolchain-versions#14-supported-libc).
There is a patchset trying to fix it: https://patchwork.ozlabs.org/project/ltp/list/?series=347760&state=*
Also, for AOSP it's better to use their fork https://android.googlesource.com/platform/external/ltp/ (noted at https://github.com/linux-test-project/ltp/wiki/Supported-kernel,-libc,-toolchain-versions#14-supported-libc).
Thanks,and could you tell me when will this patchset be merged into the master?
I've observed a delay between loop-control returning and the loop device being available on Android. I haven't been able to pinpoint exactly what is causing it yet, but I have a patch in AOSP to add a retry loop for now. https://android.googlesource.com/platform/external/ltp/+/89a1f80ca145145d37bae2372e63b9b8c646b6cb
I'm not sure if I should merge it upstream until I determine whether this is expected behavior or not.
There is a patchset trying to fix it: https://patchwork.ozlabs.org/project/ltp/list/?series=347760&state=* Also, for AOSP it's better to use their fork https://android.googlesource.com/platform/external/ltp/ (noted at https://github.com/linux-test-project/ltp/wiki/Supported-kernel,-libc,-toolchain-versions#14-supported-libc).
Thanks,and could you tell me when will this patchset be merged into the master?
Likely within the next week or two.
Merged 42ce90d8c5d80f0e629388204bbd54b108d423f2 (and 3 patches before), closing. If the problem persists, feel free to open, but beware only @edliaw will be able to do anything about it.
When testing syscall, there is a low probability of “Failed to acquire device”occurring.![image](https://user-images.githubusercontent.com/39617479/226894290-419a46f5-2f38-4d56-8631-fa4444709fcc.png)