[regression] __d_unalias() should refuse to move mountpoints

[regression] __d_unalias() should refuse to move mountpoints

[Maarten Lankhorst]

Hey Al,

Your vfs commit ee3efa91e240f513898050ef305a49a653c8ed90 caused my laptop
with a nfs root filesystem to stop working.

My testcase is simply booting through netboot with / and ~/nfs as separate
nfs filesystems, then doing 'ls ~/nfs' followed by 'ls ~' in a gnome-terminal
window, then I get:

ls: cannot access nfs: Device or resource busy

Similar things seem to happen with ls /, /dev /proc and /sys will no longer work.

Reverting this patch seems to make things work again.

~Maarten

Re: [regression] __d_unalias() should refuse to move mountpoints

[Elimar Riesebieter]

[-- Attachment #1: Type: text/plain, Size: 973 bytes --]

* Maarten Lankhorst <maarten.lankhorst@canonical.com> [2012-09-11 18:39 +0200]:

> Hey Al,
> 
> Your vfs commit ee3efa91e240f513898050ef305a49a653c8ed90 caused my laptop
> with a nfs root filesystem to stop working.
> 
> My testcase is simply booting through netboot with / and ~/nfs as separate
> nfs filesystems, then doing 'ls ~/nfs' followed by 'ls ~' in a gnome-terminal
> window, then I get:
> 
> ls: cannot access nfs: Device or resource busy
> 
> Similar things seem to happen with ls /, /dev /proc and /sys will no longer work.
> 
> Reverting this patch seems to make things work again.

I have to revert the commit as well to get my mounts working.
Without I have the same probs as described here [0].

There is no fix in 3.6-rc6. There should be one before final
release?

Thanks
Elimar

[0] http://www.spinics.net/lists/linux-nfs/msg32378.html

-- 
  The path to source is always uphill!
                                -unknown-

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]