Skip to content
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

Crash when relocating to empty chroot #3499

Open
pmatilai opened this issue Dec 19, 2024 · 0 comments
Open

Crash when relocating to empty chroot #3499

pmatilai opened this issue Dec 19, 2024 · 0 comments

Comments

@pmatilai
Copy link
Member

Ran into this while looking at something else:

Reproducer: build the reloc.spec test from the repo: rpmbuild -bb tests/data/SPECS/reloc.spec

[root@lumikko _build]# rm -rf /srv/test/; ./tools/rpm -Uv --noscripts --root /srv/test/ --nodeps --noplugins /home/pmatilai/rpmbuild/RPMS/noarch/reloc-1.0-1.noarch.rpm --relocate /opt/bin=/bin
Verifying packages...
Preparing packages...
==179835==WARNING: reading executable name failed with errno 2, some stack frames may not be symbolized
==179835==WARNING: reading executable name failed with errno 2, some stack frames may not be symbolized
/home/pmatilai/repos/rpm/lib/fprint.cc:72:32: runtime error: member access within misaligned address 0xbebebebebebebebe for type 'const struct fprintCacheEntry_s', which requires 8 byte alignment
0xbebebebebebebebe: note: pointer points here
<memory cannot be printed>
AddressSanitizer:DEADLYSIGNAL
=================================================================
==179835==ERROR: AddressSanitizer: SEGV on unknown address (pc 0x7f19222794fa bp 0x7ffdfdf21280 sp 0x7ffdfdf21240 T0)
==179835==The signal is caused by a READ memory access.
==179835==Hint: this fault was caused by a dereference of a high value address (see register values below).  Disassemble the provided pc to learn which register was used.
    #0 0x7f19222794fa  (/home/pmatilai/repos/rpm/_build/lib/librpm.so.10+0x794fa) (BuildId: 01e7aa4aefb6a69164fbf9ee1c3acf8b383dd229)
    #1 0x7f192227b743  (/home/pmatilai/repos/rpm/_build/lib/librpm.so.10+0x7b743) (BuildId: 01e7aa4aefb6a69164fbf9ee1c3acf8b383dd229)
    #2 0x7f19222872bc  (/home/pmatilai/repos/rpm/_build/lib/librpm.so.10+0x872bc) (BuildId: 01e7aa4aefb6a69164fbf9ee1c3acf8b383dd229)
    #3 0x7f19222790b8  (/home/pmatilai/repos/rpm/_build/lib/librpm.so.10+0x790b8) (BuildId: 01e7aa4aefb6a69164fbf9ee1c3acf8b383dd229)
    #4 0x7f19223a56c4  (/home/pmatilai/repos/rpm/_build/lib/librpm.so.10+0x1a56c4) (BuildId: 01e7aa4aefb6a69164fbf9ee1c3acf8b383dd229)
    #5 0x7f19223a5d20  (/home/pmatilai/repos/rpm/_build/lib/librpm.so.10+0x1a5d20) (BuildId: 01e7aa4aefb6a69164fbf9ee1c3acf8b383dd229)
    #6 0x7f1922342848  (/home/pmatilai/repos/rpm/_build/lib/librpm.so.10+0x142848) (BuildId: 01e7aa4aefb6a69164fbf9ee1c3acf8b383dd229)
    #7 0x7f19223480b3  (/home/pmatilai/repos/rpm/_build/lib/librpm.so.10+0x1480b3) (BuildId: 01e7aa4aefb6a69164fbf9ee1c3acf8b383dd229)
    #8 0x402f1f  (/home/pmatilai/repos/rpm/_build/tools/rpm+0x402f1f) (BuildId: cafa143c5e9f2fac146149c4f6d5c6b8cbf03175)
    #9 0x7f192100f247  (/lib64/libc.so.6+0x3247) (BuildId: b6c381bfdcb5e08ea82c1c39cf16580181fb6cfc)
    #10 0x7f192100f30a  (/lib64/libc.so.6+0x330a) (BuildId: b6c381bfdcb5e08ea82c1c39cf16580181fb6cfc)
    #11 0x4016b4  (/home/pmatilai/repos/rpm/_build/tools/rpm+0x4016b4) (BuildId: cafa143c5e9f2fac146149c4f6d5c6b8cbf03175)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV (/home/pmatilai/repos/rpm/_build/lib/librpm.so.10+0x794fa) (BuildId: 01e7aa4aefb6a69164fbf9ee1c3acf8b383dd229) 
==179835==ABORTING

I was expecting this to be from the fingerprint STL refactor but actually it crashes on 4.19 and 4.20 too, so who knows how old the bug is, we haven't touched either relocation or fingerprinting in ages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

1 participant