loop/010: fix the flood udev events during the test#200
Merged
kawasaki merged 4 commits intolinux-blktests:masterfrom Sep 4, 2025
Merged
loop/010: fix the flood udev events during the test#200kawasaki merged 4 commits intolinux-blktests:masterfrom
kawasaki merged 4 commits intolinux-blktests:masterfrom
Conversation
This reverts commit c4abaa2. Link: linux-blktests#181 Signed-off-by: Yi Zhang <yi.zhang@redhat.com>
There still have many udev events on some special server like [1], let's
try to stop systemd-udevd before the test, and start systemd-udevd after
the test, you can find more details on the link.
[1]
$ uname -r
6.17.0-0.rc2.250821g068a56e56fa8.27.fc44.aarch64
$ free -g
total used free shared buff/cache available
Mem: 68 0 65 0 2 67
Swap: 7 0 7
$ nproc
8
$ rpm -qa systemd
systemd-257.7-1.fc43.aarch64
$ ./check loop/010; time udevadm settle --timeout 1200
loop/010 (check stale loop partition) [passed]
runtime 91.214s ... 91.224s
real 19m37.788s
user 0m0.002s
sys 0m0.006s
Link: linux-blktests#181
Signed-off-by: Yi Zhang <yi.zhang@redhat.com>
$ ./check loop/010
loop/010 (check stale loop partition)
loop/010 (check stale loop partition) [passed]op_device}"
runtime ... 93.996s
After the fix:
$ ./check loop/010
loop/010 (check stale loop partition) [passed]
runtime 93.996s ... 93.797s
Signed-off-by: Yi Zhang <yi.zhang@redhat.com>
Signed-off-by: Yi Zhang <yi.zhang@redhat.com>
yizhanglinux
force-pushed
the
loop-010-fix
branch
from
5676268 to
32a8e41
Compare
Contributor
|
Looks good! Reviewed-by: Daniel Wagner dwagner@suse.de |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
There are still many udev events on some special servers like [1]. Let's try to stop systemd-udevd before the test and start systemd-udevd after the test to stop the udev events. You can find more details on the link.
[1]
$ uname -r
6.17.0-0.rc2.250821g068a56e56fa8.27.fc44.aarch64
$ free -g
total used free shared buff/cache available
Mem: 68 0 65 0 2 67
Swap: 7 0 7
$ nproc
8
$ rpm -qa systemd
systemd-257.7-1.fc43.aarch64
$ ./check loop/010; time udevadm settle --timeout 1200
loop/010 (check stale loop partition) [passed]
runtime 91.214s ... 91.224s
real 19m37.788s
user 0m0.002s
sys 0m0.006s
Link: #181