Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://floss.social/users/chimera_linux/statuses/112344978037478158">Chimera Linux (chimera_linux@floss.social)'s status on Sunday, 28-Apr-2024 05:15:59 JST</a><a href="https://floss.social/@chimera_linux" title="chimera_linux@floss.social"><img src="https://gnusocial.jp/avatar/160454-48-20230815165012.webp" width="48" height="48" alt="Chimera Linux" style="position: absolute; left: 0; top: 0;">Chimera Linux</a><div><a href="https://gnusocial.jp/notice/5965429" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/90966" title="bitprophet@social.coop">Jeff Forcier</a></li></ul></div></section><article><p><a href="https://hachyderm.io/@danderson">@danderson</a> <a href="https://social.treehouse.systems/@valpackett">@valpackett</a> <a href="https://aethernet.social/@nogweii">@nogweii</a> <a href="https://social.coop/@bitprophet">@bitprophet</a> there is some entirely non-portable and sketchy functionality used by systemd that imo has no justification whatsoever; for instance the way it assumes object sizes via malloc_usable_size rather than tracking its own memory properly is really bad and has bitten them even on glibc before (<a href="https://github.com/systemd/systemd/issues/22801" rel="nofollow noreferrer">https://github.com/systemd/systemd/issues/22801</a>) and the basis for using it is entirely misguided</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/3003617#notice-5965430">In conversation</a><time datetime="2024-04-28T05:15:59+09:00" title="Sunday, 28-Apr-2024 05:15:59 JST">about a year ago</time> <span>from <span><a href="https://floss.social/@chimera_linux/112344978037478158" rel="external" title="Sent from floss.social via ActivityPub">floss.social</a></span></span><a href="https://floss.social/@chimera_linux/112344978037478158">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: opengraph.githubassets.com</div><h5><a href="https://github.com/systemd/systemd/issues/22801">*** buffer overflow detected *** with GCC 12 and -D_FORTIFY_SOURCE=3 · Issue #22801 · systemd/systemd</a></h5><div></div></header><div>Using the new -D_FORTIFY_SOURCE level, I see the following buffer overflow: #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c...</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Chimera Linux (chimera_linux@floss.social)'s status on Sunday, 28-Apr-2024 05:15:59 JSTChimera Linux
in reply to
- Dave Anderson
- Jeff Forcier
@danderson @valpackett @nogweii @bitprophet there is some entirely non-portable and sketchy functionality used by systemd that imo has no justification whatsoever; for instance the way it assumes object sizes via malloc_usable_size rather than tracking its own memory properly is really bad and has bitten them even on glibc before (https://github.com/systemd/systemd/issues/22801) and the basis for using it is entirely misguided
In conversationabout a year ago from floss.socialpermalink
Attachments
1. Domain not in remote thumbnail source whitelist: opengraph.githubassets.com
  *** buffer overflow detected *** with GCC 12 and -D_FORTIFY_SOURCE=3 · Issue #22801 · systemd/systemd
  Using the new -D_FORTIFY_SOURCE level, I see the following buffer overflow: #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c...

Public

Embed Notice

HTML Code

Corresponding Notice