<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WONTFIX - src/shared/dev-setup.c is creating /dev/core symlink without checking if /proc/kcore is present" href="https://bugs.freedesktop.org/show_bug.cgi?id=65382#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WONTFIX - src/shared/dev-setup.c is creating /dev/core symlink without checking if /proc/kcore is present" href="https://bugs.freedesktop.org/show_bug.cgi?id=65382">bug 65382</a> from <a class="email" href="mailto:itumaykin@gmail.com" title="Coacher <itumaykin@gmail.com>"> Coacher</a> <pre>(In reply to <a href="show_bug.cgi?id=65382#c3">comment #3</a>) > sorry. but we do not support out-of-tree kernel patches in systemd like > this, where there's no clear perspective that they might ever go in. Please > work with the grsecurity folks first to get their patches into the kernel > proper before we can deal with this in systemd. this is true especially as > there isnt really any behavioral impliciation of not fixing this as you get > ENOENT either way. > > Sorry. Ok, even without patching vanilla kernel with grsecurity or any other hardening patches, /proc/kcore could be disabled in kernel config as a security precaution. >From my perspective I can understand different scenarios where this file is missing. Though I can not understand you desire to keep broken symlinks in /dev/ 'just because'. Does udev really need this symlink to work properly? Or maybe some other applications need it? Removing this broken symlink will trigger EACCES rather than ENOENT so my guess is no harm for applications would be done.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>