Bug 12384 - [meta][util-linux] mount: /proc: operation permitted for root only.
Summary: [meta][util-linux] mount: /proc: operation permitted for root only.
Status: RESOLVED MOVED
Alias: None
Product: Other YP Layers
Classification: Build System, Metadata & Runtime
Component: layers (show other bugs)
Version: 2.4
Hardware: Other arm
: Medium major
Target Milestone: 2.5
Assignee: Saul Wold
QA Contact:
URL:
Whiteboard: Backport 2.3.3 and 2.4.1?
Depends on:
Blocks:
 
Reported: 2017-11-28 14:54 UTC by Adrian
Modified: 2017-12-07 17:36 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
console printout (14.28 KB, text/plain)
2017-11-28 14:54 UTC, Adrian
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Adrian 2017-11-28 14:54:05 UTC
Created attachment 4133 [details]
console printout

After upgrade from pyro to rocko, there is a problem with core-image-full-cmdline image (I am enclosing a console printout). 
Apparently, there is some issue with user and kernel is not able to mount /proc causing the further errors.

The core-image-minimal image works properly. The problem is related with util-linux: if the package is excluded from core-image-full-cmdline, the image works. Unfortunately, I can't provide more logs, as terminal gets stuck.

I use the zynq-7 platform from Xilinx (master branch).
Comment 1 Saul Wold 2017-11-30 16:35:06 UTC
Hi There, 

More information is required to determine how to approach this issue. You are using the zynq-7 machine, which is not part of oe-core's normal testing, so you might want to also check with the Xilinx BSP Team (check the meta-xilinx or neta-xilinx-community layers for whom to contact).

If you can confirm that the appropriate set of PROC_FS kernel config options are set for the xilinx kernel that you are using?  It could be that the util-linux's mount requires different kernel support for /proc and what the busybox version requires?
Comment 2 Adrian 2017-12-04 16:45:17 UTC
Hi Saul,
I checked PROC_FS flags and they seem to be fine.

I think the problem is related to the fact, that `setuid` inside mount gets UID=1000 as all files are on the SD-card are owned by a first user (UID=1000). 
Once I change IDs of /bin/mount and /bin/mount.util_linux to UID=0 and GUID=0 everything works properly. 

What is strange, I don't get this error running the same image on qemu.

The SD-image is created by the wic tool. I checked earlier versions of my working SD-images and also there, all files had UID and GUID set to the first user (1000). I don't know why, in case of those older images, it was not a problem.
Comment 3 Adrian 2017-12-07 17:36:08 UTC
It seems to be problem with wic. I am investigeting.The ticket can closed.