Re: [systemd-devel] systemd-nspawn with filesystem id mapping

2021-06-08 Thread Lennart Poettering
On Fr, 04.06.21 14:53, systemd-de...@notandy.de (systemd-de...@notandy.de) wrote: > Hi again, > > after some more debugging this EOVERFLOW seems to be the result of a call to > may_o_create in fs/namei.c in the kernel. > There is a check: > > if (!fsuidgid_has_mapping(dir->dentry->d_sb,

Re: [systemd-devel] systemd-nspawn with filesystem id mapping

2021-06-04 Thread systemd-devel
Hi again, after some more debugging this EOVERFLOW seems to be the result of a call to may_o_create in fs/namei.c in the kernel. There is a check: if (!fsuidgid_has_mapping(dir->dentry->d_sb, mnt_userns)) return -EOVERFLOW; This seems to be the one returning EOVERFLOW to nspawn and

[systemd-devel] systemd-nspawn with filesystem id mapping

2021-05-30 Thread systemd-devel
Hi! I was very pleased to see the "nspawn: add support for kernel 5.12 ID mapping mounts #19438"-pull request and went right at it to try it out. The following was tested on the current git head of systemd running on archlinux. What I try to achieve on a high level is kind of emulating