From: Smalley <stephen.smalley.work@gmail.com>
To: selinux@vger.kernel.org
Cc: Stephen Smalley <stephen.smalley.work@gmail.com>
Subject: [PATCH] libsemanage: fsync before rename
Date: Wed, 13 May 2020 14:46:08 -0400 [thread overview]
Message-ID: <5ebc4079.1c69fb81.c8782.38eb@mx.google.com> (raw)
From: Stephen Smalley <stephen.smalley.work@gmail.com>
Prior to rename(2)'ing new files into place, fsync(2) them to ensure
the contents will be fully written prior to rename. While we are here,
also fix checking of write(2) to detect short writes. This code could
be more generally improved but keeping to the minimal changes required
to fix this bug.
Fixes: https://github.com/SELinuxProject/selinux/issues/237
Signed-off-by: Stephen Smalley <stephen.smalley.work@gmail.com>
---
libsemanage/src/semanage_store.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/libsemanage/src/semanage_store.c b/libsemanage/src/semanage_store.c
index 859c0a22..3cac36d4 100644
--- a/libsemanage/src/semanage_store.c
+++ b/libsemanage/src/semanage_store.c
@@ -735,7 +735,7 @@ int semanage_copy_file(const char *src, const char *dst, mode_t mode)
}
umask(mask);
while (retval == 0 && (amount_read = read(in, buf, sizeof(buf))) > 0) {
- if (write(out, buf, amount_read) < 0) {
+ if (write(out, buf, amount_read) != amount_read) {
errsv = errno;
retval = -1;
}
@@ -745,6 +745,10 @@ int semanage_copy_file(const char *src, const char *dst, mode_t mode)
retval = -1;
}
close(in);
+ if (fsync(out) < 0) {
+ errsv = errno;
+ retval = -1;
+ }
if (close(out) < 0) {
errsv = errno;
retval = -1;
--
2.23.3
next reply other threads:[~2020-05-13 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 18:46 Smalley [this message]
2020-05-13 18:52 ` [PATCH] libsemanage: fsync before rename Nicolas Iooss
2020-05-13 19:08 ` Stephen Smalley
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=5ebc4079.1c69fb81.c8782.38eb@mx.google.com \
--to=stephen.smalley.work@gmail.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.