I figured I would give a hardlink a shot from the bind mount from /pro/<pid> to /data back to /data... and it failed per my expectations, "cross link device".
On Fri, Jul 5, 2013 at 11:58 AM, William Roberts <[email protected]>wrote: > bind mount seems to not care about the context option > > root@maguro:/data # touch > a > root@maguro:/data # touch b > root@maguro:/data # mount -obind,context=u:object_r:mqueue:s0 a b > root@maguro:/data # ls -Z a > -rw-rw-rw- root root u:object_r:system_data_file:s0 a > root@maguro:/data # ls -Z > b > -rw-rw-rw- root root u:object_r:system_data_file:s0 b > > > I was initially trying to bind mount stuff out of /proc and apply a > separate label to it, and it didn't work. Any idea on how to bind mount a > file, from /proc/<pid> (no xattr support) and provide a separate label for > the entity? > > > -- > Respectfully, > > William C Roberts > > -- Respectfully, William C Roberts
