All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Harry G. Coin" <hgcoin@gmail.com>
To: virtio-fs-list <virtio-fs@redhat.com>
Subject: [Virtio-fs] regression: lsetfilecon fails, breaks rpm, dpkg, dnf in virtiofs guests.
Date: Sat, 29 May 2021 13:42:50 -0500	[thread overview]
Message-ID: <e1437314-4870-a3a3-e866-8be50282ce3c@gmail.com> (raw)

Some regression in virtio-fs has led to rpm/dnf/yum failing  in the same
guest it previously worked.

linux 5.11.19-300.fc34.x86_64

Specifically, all attempts to use dnf/yum lead to examples similar to this:

Error unpacking rpm package dnf-4.7.0-1.fc34.noarch
  Upgrading        :
python3-dnf-plugins-core-4.0.21-1.fc34.noarch                                                                                                                                                     
8/20
error: unpacking of archive failed on file /usr/bin/dnf;60b1b277: cpio:
(error 0x2)
error: dnf-4.7.0-1.fc34.noarch: install failed
error: lsetfilecon: (/etc/dnf/plugins/copr.conf,
system_u:object_r:etc_t:s0) Operation not permitted
error: Plugin selinux: hook fsm_file_prepare failed

(

For all packages.  No updates are possible.  Possibly related to:
https://github.com/fedora-selinux/selinux-policy/pull/478/files/21a2df26cd605c55de7edc80e16907fcb76ccf08 
?  What really gets me, is this error exists even though

# getenforce
Permissive

)

The host is running btrfs.  ... virtiofsd --fd=50 -o
source=/vmsystems/fedora_generic,xattr,flock,posix_lock

same effect with  .... virtiofsd --fd=36 -o
source=/vmsystems/dbl1,xattr,flock,no_posix_lock

/etc/fstab:

myfs / virtiofs seclabel 0 0





             reply	other threads:[~2021-05-29 18:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-29 18:42 Harry G. Coin [this message]
2021-06-01 13:02 ` [Virtio-fs] regression: lsetfilecon fails, breaks rpm, dpkg, dnf in virtiofs guests Vivek Goyal
2021-06-01 17:33   ` Ondrej Mosnacek
2021-06-03 17:58   ` Harry G. Coin

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=e1437314-4870-a3a3-e866-8be50282ce3c@gmail.com \
    --to=hgcoin@gmail.com \
    --cc=virtio-fs@redhat.com \
    /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.