common/rc: fix check for disabled kmemleak
PATCH 1/1 common/rc: fix check for disabled kmemleak
With kernel commit b353756b2b71 ("kmemleak: always register debugfs file") that was merged to v4.19-rc3, the kmemleak debugfs knob exists even if kmemleak is disabled, but returns EBUSY on write.
Suppress EBUSY errors from _check_kmemleak() by removing write permission from knob on failure to initialize kmemleak.
---
Guys,
With kernel v4.19-rc3, tests started printing noisy messages about failure to write to kmemleak knob.
Problem is that kmemleak was disabled on my system but the test for kmemleak enabled we have in place was broken by the kernel change.
I tried this patch to hack around the new kernel behavior, but something is broken in this patch as it doesn't suppress all errors. For me, I prefer to have kmemleak enabled anyway, so I gave up on this hack and enabled kmemleak.
If someone is interested in taking over, be my guest.
FYI, to enable kmemleak on kvm-xfstests I needed to configure CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE=5000
# CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFF is not set
Thanks,
Amir.
common/rc | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
common/rc +8 -2
@@ -3514,8 +3514,14 @@ _init_kmemleak() # Disable the automatic scan so that we can control it completely, # then dump all the leaks recorded so far. - echo "scan=off" > "$kern_knob" - _capture_kmemleak /dev/null + if echo "scan=off" > "$kern_knob" 2>/dev/null; then + _capture_kmemleak /dev/null + else + # Since kernel v4.19-rc3, the knob exists even if kmemleak is + # disabled, but returns EBUSY on write. Suppress EBUSY errors + # from _check_kmemleak() by removing write permission from knob + chmod a-w "$kern_knob" + fi } # check kmemleak log
Signature · 1 line
2.17.1
Quoted 8 lines · Amir Goldstein
With kernel commit
b353756b2b71("kmemleak: always register debugfs file") that was merged to v4.19-rc3, the kmemleak debugfs knob exists even if kmemleak is disabled, but returns EBUSY on write.Suppress EBUSY errors from
_check_kmemleak()by removing write permission from knob on failure to initialize kmemleak.Signed-off-by Amir Goldstein <[email protected]>
Ewww, but I guess it works... :)
--D
Quoted 51 lines
---
Guys,
With kernel v4.19-rc3, tests started printing noisy messages about failure to write to kmemleak knob.
Problem is that kmemleak was disabled on my system but the test for kmemleak enabled we have in place was broken by the kernel change.
I tried this patch to hack around the new kernel behavior, but something is broken in this patch as it doesn't suppress all errors. For me, I prefer to have kmemleak enabled anyway, so I gave up on this hack and enabled kmemleak.
If someone is interested in taking over, be my guest.
FYI, to enable kmemleak on kvm-xfstests I needed to configure
CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE=5000
#CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFFis not setThanks,
Amir.common/rc | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)common/rc +8
-2@@ -3514,8 +3514,14 @@ _init_kmemleak() # Disable the automatic scan so that we can control it completely, # then dump all the leaks recorded so far. - echo "scan=off" > "$kern_knob" - _capture_kmemleak /dev/null + if echo "scan=off" > "$kern_knob" 2>/dev/null; then + _capture_kmemleak /dev/null + else + # Since kernel v4.19-rc3, the knob exists even if kmemleak is + # disabled, but returns EBUSY on write. Suppress EBUSY errors + # from _check_kmemleak() by removing write permission from knob + chmod a-w "$kern_knob" + fi } # check kmemleak logSignature · 1 line
2.17.1
Quoted 6 lines · Darrick J. Wong
Quoted 4 lines · Amir Goldstein
With kernel commit
b353756b2b71("kmemleak: always register debugfs file") that was merged to v4.19-rc3, the kmemleak debugfs knob exists even if kmemleak is disabled, but returns EBUSY on write.
Quoted 7 lines
Quoted 4 lines
Suppress EBUSY errors from
_check_kmemleak()by removing write permission from knob on failure to initialize kmemleak.Signed-off-by Amir Goldstein <[email protected]>Ewww, but I guess it works... :)
Ewww indeed, but what I wrote below is that it doesn't work, but I couldn't figure out why.
In manual tests the method works, but some elusive detail in the scripts must have escaped me and I still get some EBUSY errors when running with this patch and kmemleak disabled.
Thanks,
Amir.
Quoted 54 lines
--D
Quoted 51 lines
---
Guys,
With kernel v4.19-rc3, tests started printing noisy messages about failure to write to kmemleak knob.
Problem is that kmemleak was disabled on my system but the test for kmemleak enabled we have in place was broken by the kernel change.
I tried this patch to hack around the new kernel behavior, but something is broken in this patch as it doesn't suppress all errors. For me, I prefer to have kmemleak enabled anyway, so I gave up on this hack and enabled kmemleak.
If someone is interested in taking over, be my guest.
FYI, to enable kmemleak on kvm-xfstests I needed to configure
CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE=5000
#CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFFis not setThanks,
Amir.common/rc | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)common/rc +8
-3@@ -3514,8 +3514,14 @@ _init_kmemleak() # Disable the automatic scan so that we can control it completely, # then dump all the leaks recorded so far. - echo "scan=off" > "$kern_knob" - _capture_kmemleak /dev/null + if echo "scan=off" > "$kern_knob" 2>/dev/null; then + _capture_kmemleak /dev/null + else + # Since kernel v4.19-rc3, the knob exists even if kmemleak is + # disabled, but returns EBUSY on write. Suppress EBUSY errors + # from _check_kmemleak() by removing write permission from knob + chmod a-w "$kern_knob" + fi } # check kmemleak log --2.17.1
Quoted 12 lines · Amir Goldstein
With kernel commit
b353756b2b71("kmemleak: always register debugfs file") that was merged to v4.19-rc3, the kmemleak debugfs knob exists even if kmemleak is disabled, but returns EBUSY on write.Suppress EBUSY errors from
_check_kmemleak()by removing write permission from knob on failure to initialize kmemleak.Signed-off-by Amir Goldstein <[email protected]>---
Guys,
Quoted 8 lines
With kernel v4.19-rc3, tests started printing noisy messages about failure to write to kmemleak knob.
Problem is that kmemleak was disabled on my system but the test for kmemleak enabled we have in place was broken by the kernel change.
I tried this patch to hack around the new kernel behavior, but something is broken in this patch as it doesn't suppress all errors.
I guess that's because root has writable permission even if the file has no 'w' permission bit set, i.e the "if [ ! -w $kern_knob ]" check never triggers even if we "chmod a-w $kern_knob".
But, on the other hand, I prefer not changing a system file's permission in test (even if it could hack around the issue). Checking if a special file exists would be better, like what we do in _check_dmesg and _check_filesystems.
For example, touch $RESULT_BASE/check_kmemleak in _init_kmemleak if kmemleak is available, remove the file otherwise. Note that we cannot create this file in $RESULT_DIR like other similar checks because it's not initialized at _init_kmemleak time.
Thanks,
Eryu
Quoted 39 lines
For me, I prefer to have kmemleak enabled anyway, so I gave up on this hack and enabled kmemleak.
If someone is interested in taking over, be my guest.
FYI, to enable kmemleak on kvm-xfstests I needed to configure
CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE=5000
#CONFIG_DEBUG_KMEMLEAK_DEFAULT_OFFis not setThanks,
Amir.common/rc | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)common/rc +8
-2@@ -3514,8 +3514,14 @@ _init_kmemleak() # Disable the automatic scan so that we can control it completely, # then dump all the leaks recorded so far. - echo "scan=off" > "$kern_knob" - _capture_kmemleak /dev/null + if echo "scan=off" > "$kern_knob" 2>/dev/null; then + _capture_kmemleak /dev/null + else + # Since kernel v4.19-rc3, the knob exists even if kmemleak is + # disabled, but returns EBUSY on write. Suppress EBUSY errors + # from _check_kmemleak() by removing write permission from knob + chmod a-w "$kern_knob" + fi } # check kmemleak logSignature · 1 line
2.17.1