Skip to content

RFC Possible solution to possible regression

James Carter selinux 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest2 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2libselinux: Close old selabel handle when setting a new onelibselinux/src/selinux_restorecon.c+4 -00 replies
2/2libsemanage: Set new restorecon handle before doing restoreconlibsemanage/src/semanage_store.c+5 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [RFC PATCH 0/2] Possible solution to possible regression

As reported by Petr Lautrbach ([email protected]), commit d96f27bf7cb9 ("libsemanage: Preserve file context and ownership in policy store") can cause restorecon to use old data.

Here is a possible fix. It seems to work.

James Carter (2):
libselinux: Close old selabel handle when setting a new one
libsemanage: Set new restorecon handle before doing restorecon

 libselinux/src/selinux_restorecon.c | 4 ++++
 libsemanage/src/semanage_store.c    | 5 +++++
 2 files changed, 9 insertions(+)
Signature · 1 line
2.48.1