Re: Potential smb/dfs regression introduced in kernel 6.6

[Greg KH <gregkh@linuxfoundation.org>]

On Thu, Jun 27, 2024 at 01:28:29PM +0000, Steinbeißer, Sebastian wrote:
> #regzbot introduced: v6.6
> 
> Dear Kernel developers,
> 
> I'm a NetApp storage admin and we started receiving reports by our
> customers that subvolumes of exported volumes can no longer be accessed
> transparently but need to be mounted separately.
> 
> The way this works with NetApp is that a volume, e.g., myvol, within
> the storage virtual machine (SVM - vserver) is exported and can be
> accessed by mounting //SVM_IP/myvol into, e.g., /mnt/myvol
> Subvolumes can be added to the junction path, e.g., mysubvol can be
> mounted under myvol and used to be transparently accessable via
> /mnt/myvol/mysubvol just like any directory within myvol would be.
> This now is no longer the case and the subvolume needs to be mounted
> separately.
> 
> This has started when customers upgraded distributions that shipped
> with kernel >=6.6.
> https://wiki.samba.org/index.php/LinuxCIFSKernel#6.6_(module_version_2.45)_(47_changesets)
> 
> We've been able to reproduce the behavior with Fedora/Ubuntu and
> kernels 6.6 to 6.9.

Any chance you can use 'git bisect' to find the offending change if you
can reproduce this?  And you might want to cc: the smbfs maintainers.

thanks,

greg k-h