-
Notifications
You must be signed in to change notification settings - Fork 246
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
lxcfs: handle NULL in lxcfs_read (segfault at 0, code=killed, status=11/SEGV) #635
Comments
@deleriux @mihalicyn @brauner |
Hello, my partner and I are UT Austin students and would like to work on this problem for a class project. Could we know more about how this issue can be recreated so we can try debugging it? |
I am working with anooprac |
Hi @anooprac , it only happened on 2 nodes within a cluster with thousands of machines. I still cannot reproduce it from my side manually. |
Hi @81981266 thanks for your report! This is a very interesting issues, because as I can see from callstack My theory is that it can be a very tricky bug in dynamic symbol resolution (the Another good question is that even if Can you provide me with your crash dump file and your LXCFS binary so I can go through the crash-dump and analyze it? |
Hello @mihalicyn , thanks for your comment. OS VERSION="20.04.6 LTS (Focal Fossa)" |
It is sad news.
In general I can't see any issues with your version of the code. Let's then wait for the next crash reproduction and crash-dump file. Also, I would strongly recommend updating to the recent LXCFS version from 4.0.11. I mark this issue as "incomplete" as we don't have enough information to debug this right now. |
Is it still useful to update the repo to use the macros instead of strcmp for the paths? |
I think it is. It also makes sense to do this for all fuse callbacks (except |
Sounds good. I'll add the fixes for the rest of the FUSE callbacks once the lxcfs_read() changes pass. |
os:
ubuntu 5.15.0-52
lxcfs version:
4.0.11
lxcfs is killed by
11/SEGV
signal, thesyslog
is as below:the core dump explained by
![SeaTalk_IMG_20240424_171648](https://private-user-images.githubusercontent.com/36359920/325159030-d419bda0-fa85-4b39-bc6e-cc2d564c712a.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA1NzYzNDUsIm5iZiI6MTcyMDU3NjA0NSwicGF0aCI6Ii8zNjM1OTkyMC8zMjUxNTkwMzAtZDQxOWJkYTAtZmE4NS00YjM5LWJjNmUtY2MyZDU2NGM3MTJhLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MTAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzEwVDAxNDcyNVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTA3ZmRiMjA1ZTkwYzgzNTRhNzU3YzRkYmU0ODdmMDQ4ZWNlMzVlMzkzMGVkOWMwMDNmYjY0M2VlMThmZDg2YjYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.7zwk6MI-weEnI2Z_z6ndI4Dd9yNsOVx1HJnSxuxbz3o)
gbd
from/var/crash
folder is as below:The code of
lxcfs.c:778
is here: https://github.com/lxc/lxcfs/blob/lxcfs-4.0.11/src/lxcfs.c#L778A similar issue about 'NULL path in lxcfs_releasedir/lxcfs_release' fix: #577
The text was updated successfully, but these errors were encountered: