New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.34-rc1: lsblk: malloc(): unsorted double linked list corrupted #787
Comments
I tried to reproduce the problem after enabling address sanitizer:
And without atexit() hook.
But unfortunately all I can see is couple memory leaks.
Maybe something with number of block devices, or some other environmental aspect is required to trigger the bug and I simply do not have it. @balducci I wonder if you recompile the same way I did and perhaps corruption is reported easier to understand manner. |
after rebuilding with clang and CFLAGS='-fsanitize=address -ggdb' I
|
Please, try also "LSBLK_DEBUG=all lsblk". It will provide more details. |
I probably see the problem...
We definitely need dev = NULL, after lsblk_devtree_remove_device(). |
Addresses: #787 Signed-off-by: Karel Zak <kzak@redhat.com>
Fixed (I hope). Please, try the current git tree. I guess you have a ram disk device, in this case the default exclude filter is applied and the device ignored. |
AFAICS, that seems to have fixed things: no problems after running thank you very much |
Thanks for your report and testing! |
hello
I'm getting this error at run time from lsblk from 2.34-rc1:
The error isn't reproducible: I would say that it shows up ~50% of the
times.
Maybe worth to note: I couldn't trigger the error under gdb, even after
running the command many times (I guess there might be good reasons
for this)
Needless to say: no problem whatsoever when running lsblk from 2.33.2.
My specs follow:
thanks a lot
ciao
-gabriele
The text was updated successfully, but these errors were encountered: