On Wed, Jan 12, 2011 at 09:50:57AM +0100, Santiago Garcia Mantinan wrote: > I've been also hit by this bug and saw the forwarding that Christian did > upstream and I'm afraid that if upstream didn't look at our bug they may not > be getting the spirit of it.
> In fact, upstream bugtrack shows Jeff Layton asking: > I suppose we could disallow this somehow, but *should* we? Is this > specifically disallowed? That's in reference to allowing a share to be mounted multiple times at a mount point. I don't think that should be disallowed; it's not disallowed for other filesystem types either, though you may be unable to double-mount a given device due to locking issues. > I don't see a problem in mount.cifs allowing to mount the same share on the > same mountpoint other than "mount -a" mounting things several times. > In fact, I used to relly on "mount -a" exit status to know if I have > everything mounted or not, and with this bug you cannot issue a "mount -a" > as you'll get all the cifs shares mounted again. I believe this is only the case when the path written to /etc/mtab differs from that in /etc/fstab - most commonly because of the extra / that gets appended to the /etc/mtab entry with recent versions of mount.cifs. This is a behavior change that doesn't make much sense (it's inconsistent with NFS mtab handling, for instance), but I'm not sure we're going to get it reverted soon enough to make a difference. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: Digital signature
