On 2014-10-07 21:58:28 +0200, Andreas Henriksson wrote: > Control: tag -1 upstream confirmed wontfix > > Hello Kusanagi Kouichi. > > Thanks for your bug report. > > On Tue, Oct 07, 2014 at 10:21:55AM +0000, Kusanagi Kouichi wrote: > > Package: mount > > Version: 2.25.1-3 > > Severity: normal > > > > Since I upgraded mount from 2.20.1-5.11 to 2.25.1-3, > > (And during this big version-gap jump mount was completely > rewritten on top of a new libmount implementation.) > > > "mount --bind -o remount" doesn't preserve flags anymore. > > Is there a reason you include the --bind argument here?
Actually mount runs inside a new namespace. And remount without --bind fails with EPERM inside a new namespace. Now it fails even with --bind. > That is as far as I can tell the culprit and things should > just work if you don't (but ofcourse the behavioural change > is unfortunate and I don't know if it's on purpose). > > > If you still want to attempt restoring the old behaviour I would > start looking at the following code in the end of sys-utils/mount.c > > if (oper || propa) > /* For --make-* or --bind is fstab unnecessary */ > mnt_context_set_optsmode(cxt, MNT_OMODE_NOTAB); > > > Also, unless you're satisfied with not including --bind then > I suggest you bring this discussion to the upstream developers > who should be able to give you better advice then me. Please > try [email protected] .... Just alerting them of the > behavioural change might be a good idea either way. > > Hopefully just dropping the --bind argument should satisfy your > needs though. > > Regards, > Andreas Henriksson -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
