Skip to content

warning working around a Linux kernel bug by creating a hole #92

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

Open
rkanavath opened this issue Apr 7, 2016 · 12 comments
Open

warning working around a Linux kernel bug by creating a hole #92

rkanavath opened this issue Apr 7, 2016 · 12 comments

Comments

@rkanavath
Copy link

patchelf --set-rpath /opt/lib /opt/lib/libQtCore.so.4.8.7
warning: working around a Linux kernel bug by creating a hole of 2088960 bytes in ‘/opt/lib//libQtCore.so.4.8.7’

I am using patchelf 0.9

I saw a related bug here: #47 and its fix f6886c2

But that didn't solved my issue.

size of libQtCore.so.4.8.7 is only 3.1 M

@xiaosuo
Copy link
Contributor

xiaosuo commented Dec 6, 2016

Was the result binary usable or you complained about the waning message?

@kr411
Copy link

kr411 commented Dec 7, 2016

Hi xiaosuo,

I am also facing similar issue for setting interpreter and rpath for libpthread.so.0, Warning message as shown below

  • warning: working around a Linux kernel bug by creating a hole of 6976632 bytes in '/lib/libpthread.so.0'.

I would like to understand the significance of creating a hole of X bytes in the library.

Thanks in advance.

@xiaosuo
Copy link
Contributor

xiaosuo commented Dec 7, 2016

In fact, nothing bad will happen except for size bloating, because patchelf handles it for you. Just take it easy and ignore these warning messages.

I submitted a PR for these annoying messages.

See #111

@kr411
Copy link

kr411 commented Dec 8, 2016

Hi xiaosuo,

Thanks for the quick response.

I would like to know some additional information.

I am curious to know why the file bloating is required for dynamic libraries which is happening in the function rewriteSectionsLibrary().

Thanks in advance.

@JonathonReinhart
Copy link

This appears to be obsolete, as the message is no longer present in current master (2a9cefd).

@JonathonReinhart
Copy link

@xiaosuo Can this issue be closed also? As you mentioned, this is fixed by c4deb5e.

@xiaosuo
Copy link
Contributor

xiaosuo commented Jun 17, 2017

Yes.

@sjackman
Copy link

Is it time to tag a stable release that includes c4deb5e?

@pratikpparikh
Copy link

Is this fixed?

@sjackman
Copy link

sjackman commented Jan 1, 2019

My understanding is that it's fixed in master in commit
c4deb5e but it's not yet fixed in a stable release.

@sandorex
Copy link

sandorex commented Dec 24, 2019

Ubuntu 18.04 has 0.9 in the repositories but i still have the same issue

EDIT: And the executable isn't runnable anymore

@sjackman
Copy link

sjackman commented Jan 2, 2020

patchelf 0.10 was released on 2019-03-28: https://github.com/NixOS/patchelf/releases/tag/0.10

sdinot pushed a commit to orfeotoolbox/OTB that referenced this issue Aug 5, 2021
sdinot pushed a commit to orfeotoolbox/OTB that referenced this issue Aug 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants