Bug 26354 - rpm unpacking fails on f2fs and nilfs2
Summary: rpm unpacking fails on f2fs and nilfs2
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-17 16:56 CET by Thierry Vignaud
Modified: 2020-03-18 09:44 CET (History)
1 user (show)

See Also:
Source RPM: kernel-5.5.9-1.mga8.src.rpm
CVE:
Status comment:

Attachments
report.bug for the F2FS case (144.66 KB, application/x-xz)
2020-03-17 16:58 CET, Thierry Vignaud 		Details
report.bug for the NILFS2 case (143.44 KB, application/x-xz)
2020-03-17 17:00 CET, Thierry Vignaud 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Thierry Vignaud 2020-03-17 16:56:10 CET 
Description of problem:
While trying to do some install over nilfs & f2fs (the later not being "upstreamed" in drakx yet), I see package installation fails with:
"cap_set_file failed - Resource temporarily unavailable"
and:
"cpio: symlink failed - Resource temporarily unavailable"

It always fails when using / formatted as nilfs or f2fs.
It always succeeds when using / formatted as ext4.

Examples:

unpacking of archive failed on file /usr/bin/newgidmap;5e70d81f: cpio: cap_set_file failed - Resource temporarily unavailable

unpacking of archive failed on file /usr/lib/.build-id/66/d50621a56de287196eaf685be6af995d43fe8c;5e70d81f: cpio: symlink failed - Resource temporarily unavailable

I wonder if we shouldn't set:
CONFIG_F2FS_FS_SECURITY=y
(but that wouldn't fix nilfs2)

And maybe "FS_DAX_PMD" (which needs CONFIG_ZONE_DEVICE=y) but I've no clue there
Thierry Vignaud 2020-03-17 16:58:16 CET

CC: (none) => pterjan

Comment 1 Thierry Vignaud 2020-03-17 16:58:44 CET 
Created attachment 11552 [details]
report.bug for the F2FS case
Comment 2 Thierry Vignaud 2020-03-17 17:00:36 CET 
Created attachment 11553 [details]
report.bug for the NILFS2 case
Comment 3 Thomas Backlund 2020-03-17 20:45:10 CET 
Yeah, F2FS_FS_SECURITY should fix F2FS

but nilfs2 does not support extended atributes yet, so I think you will have to ignore that one for now...
Comment 4 Thomas Backlund 2020-03-17 21:17:22 CET 
ZONE_DEVICE & co enabled, including FS_DAX_PMD
Comment 5 Thierry Vignaud 2020-03-18 08:56:45 CET 
BTW I confirm that F2FS_FS_SECURITY fixes f2fs.
But not nilfs2 obviously.
That's the only change I did yesterday, I didn't experimented with other changes for nilfs2.
I'll wait for your next kernel.
Comment 6 Thierry Vignaud 2020-03-18 09:44:55 CET 
I'll close that one then

Resolution: (none) => FIXED
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.