summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEric Biggers <ebiggers@google.com>2020-10-15 14:52:54 -0700
committerEric Biggers <ebiggers@google.com>2020-10-15 15:26:27 -0700
commit10724d93a1ee63109c0354c60b0975e13c6c8a85 (patch)
tree893a3c9a147de784629e0072730187d66a93a62a
parente9023dc7bb621e4edd5b02cdf58f98579ebcd8f7 (diff)
downloadvold-10724d93a1ee63109c0354c60b0975e13c6c8a85.tar.gz
Silence useless LOOP_GET_STATUS64 warnings
When vold starts up, there are lots of warnings like: W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop30: No such device or address W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop29: No such device or address W vold : Failed to LOOP_GET_STATUS64 /dev/block/loop28: No such device or address vold is iterating through all loop devices and unbinding the file from any vold-managed ones. It's expected that not all loop devices have a file bound to them, however. On these, LOOP_GET_STATUS64 fails with ENXIO. Don't print a warning in such cases. Change-Id: I91755259dc2c09b1869627259d1e59d5edd6f145
-rw-r--r--Loop.cpp4
1 files changed, 3 insertions, 1 deletions
diff --git a/Loop.cpp b/Loop.cpp
index 9fa876ce..87f105df 100644
--- a/Loop.cpp
+++ b/Loop.cpp
@@ -150,7 +150,9 @@ int Loop::destroyAll() {
struct loop_info64 li;
if (ioctl(fd.get(), LOOP_GET_STATUS64, &li) < 0) {
- PLOG(WARNING) << "Failed to LOOP_GET_STATUS64 " << path;
+ if (errno != ENXIO) {
+ PLOG(WARNING) << "Failed to LOOP_GET_STATUS64 " << path;
+ }
continue;
}