Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1849147

Summary:	virtiofsd: Allow setting trusted attributes for containers in containers
Product:	Red Hat Enterprise Linux Advanced Virtualization	Reporter:	Dr. David Alan Gilbert <dgilbert>
Component:	qemu-kvm	Assignee:	Dr. David Alan Gilbert <dgilbert>
qemu-kvm sub component:	virtio-fs	QA Contact:	xiagao
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	medium
Priority:	medium	CC:	ailan, coli, jinzhao, juzhang, lijin, stefanha, vgoyal, virt-maint, xiagao
Version:	8.3	Flags:	pm-rhel: mirror+
Target Milestone:	rc
Target Release:	8.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 18:10:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dr. David Alan Gilbert 2020-06-19 17:22:27 UTC

Description of problem:

In 8.2.1 I backported Stefan's code that drops a lot of capabilities for the virtiofsd;  unfortunately Vivek noticed that it's needed by a guest overlayfs which sets trusted.* capabilities on the underlying fs.

I've got a current hack that conditionally undoes the capability setting that Stefan added; which might be OK as an initial work around.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 6 Dr. David Alan Gilbert 2020-10-27 18:10:47 UTC

I'm duping this one to bz 1860491 - the xattrmapping system is now upstream

*** This bug has been marked as a duplicate of bug 1860491 ***