linux-kernel - Re: [PATCH review 23/85] ocfs2: Convert uid and gids between in core and on disk inodes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 14 Feb 2013 01:10:01 -0800
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	linux-fsdevel@...r.kernel.org
Cc:	Linux Containers <containers@...ts.linux-foundation.org>,
	linux-kernel@...r.kernel.org, "Serge E. Hallyn" <serge@...lyn.com>,
	Mark Fasheh <mfasheh@...e.com>
Subject: Re: [PATCH review 23/85] ocfs2: Convert uid and gids between in core and on disk inodes

Joel Becker <jlbec@...lplan.org> writes:

> This has the same problem with two machines in different userspace
> namespaces.  Should this be punted to the sysadmin or helped out in the
> filesystem?  Do you define this case as unsupported?

First I define two machines in the same user namespace as two machines
with synchronized password files.

As today connecting two machines without synchronizing the password
entries is a problem, won't work, and is punted to the sysadmin to make
keep from doing something silly.

At the same time I don't want to make it easy to get confused, or cause
breakage.

With these patches ocfs2 only still only works in the initial user
namespace.  I don't set .fs_flags = FS_USERNS_MOUNT in struct
filesystem.  Which means that while users in other user namespaces can
store files on ocfs2, they can't mount ocfs2.

Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/