From: Petr Lautrbach <lautrbach@redhat.com>
To: selinux@vger.kernel.org
Subject: [SELinuxProject/selinux] The SIGBUS signal is triggered because the status page is incorrectly written. (Issue #475)
Date: Tue, 06 May 2025 14:18:14 +0200 [thread overview]
Message-ID: <87bjs60w6x.fsf@redhat.com> (raw)
In-Reply-To: SELinuxProject/selinux/issues/475@github.com
biubiuzy created an issue (SELinuxProject/selinux#475) - https://github.com/SELinuxProject/selinux/issues/475
selinux_status_open() open the kernel status page and mmap it with
read-only mode, If the file is truncated(i.e echo 1 > /sys/fs/selinux/status), this causes subsequent calls to selinux_status_* interfaces to trigger the sigbus signal.
See also https://github.com/systemd/systemd/issues/37349
parent reply other threads:[~2025-05-06 12:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <SELinuxProject/selinux/issues/475@github.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bjs60w6x.fsf@redhat.com \
--to=lautrbach@redhat.com \
--cc=selinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.