From: Petr Lautrbach <plautrba@redhat.com>
To: SElinux list <selinux@vger.kernel.org>
Cc: Nicolas Iooss <nicolas.iooss@m4x.org>
Subject: Re: [PATCH v3] libsemanage: sync filesystem with sandbox
Date: Mon, 01 Feb 2021 15:12:56 +0100 [thread overview]
Message-ID: <87mtwnswpj.fsf@redhat.com> (raw)
In-Reply-To: <CAJfZ7=kpTbkjZPF7MdgxshvfbSWumN5+iMdAcN7Cypm6aiqH8w@mail.gmail.com>
Nicolas Iooss <nicolas.iooss@m4x.org> writes:
> On Sun, Jan 31, 2021 at 12:53 PM Petr Lautrbach <plautrba@redhat.com> wrote:
>>
>> Commit 331a109f91ea ("libsemanage: fsync final files before rename")
>> added fsync() for policy files and improved situation when something
>> unexpected happens right after rename(). However the module store could
>> be affected as well. After the following steps module files could be 0
>> size:
>>
>> 1. Run `semanage fcontext -a -t var_t "/tmp/abc"`
>> 2. Force shutdown the server during the command is run, or right after
>> it's finished
>> 3. Boot the system and look for empty files:
>> # find /var/lib/selinux/targeted/ -type f -size 0 | wc -l
>> 1266
>>
>> It looks like this situation can be avoided if the filesystem with the
>> sandbox is sync()ed before we start to rename() directories in the
>> store.
>>
>> Signed-off-by: Petr Lautrbach <plautrba@redhat.com>
>
> Acked-by: Nicolas Iooss <nicolas.iooss@m4x.org>
>
Merged.
> Thanks!
> Nicolas
>
>> ---
>>
>> - syncfs() moved before rename() dance
>>
>> libsemanage/src/semanage_store.c | 13 +++++++++++++
>> 1 file changed, 13 insertions(+)
>>
>> diff --git a/libsemanage/src/semanage_store.c b/libsemanage/src/semanage_store.c
>> index cd5e46bb2401..c6a736fe2d26 100644
>> --- a/libsemanage/src/semanage_store.c
>> +++ b/libsemanage/src/semanage_store.c
>> @@ -1736,6 +1736,19 @@ static int semanage_commit_sandbox(semanage_handle_t * sh)
>> }
>> close(fd);
>>
>> + /* sync changes in sandbox to filesystem */
>> + fd = open(sandbox, O_DIRECTORY);
>> + if (fd == -1) {
>> + ERR(sh, "Error while opening %s for syncfs(): %d", sandbox, errno);
>> + return -1;
>> + }
>> + if (syncfs(fd) == -1) {
>> + ERR(sh, "Error while syncing %s to filesystem: %d", sandbox, errno);
>> + close(fd);
>> + return -1;
>> + }
>> + close(fd);
>> +
>> retval = commit_number;
>>
>> if (semanage_get_active_lock(sh) < 0) {
>> --
>> 2.30.0
>>
prev parent reply other threads:[~2021-02-01 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210131110251.300553-1-plautrba@redhat.com>
2021-01-31 17:45 ` [PATCH v3] libsemanage: sync filesystem with sandbox Nicolas Iooss
2021-02-01 14:12 ` Petr Lautrbach [this message]
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=87mtwnswpj.fsf@redhat.com \
--to=plautrba@redhat.com \
--cc=nicolas.iooss@m4x.org \
--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.