DFS mount does not pass context option to actual share mounts
Subsystems (2)
A message that is not in the archive (sent off-list or not yet received): [email protected]/
https://bugzilla.samba.org/show_bug.cgi?id=14201
--- Comment #1 from Paulo Alcantara <[email protected]> --- Hi Patrick,
Does this still occur with mainline kernel?
Signature · 2 lines
You are receiving this mail because: You are the QA Contact for the bug.
https://bugzilla.samba.org/show_bug.cgi?id=14201
--- Comment #2 from Patrick Böker <[email protected]> --- Hi Paulo,
have there been patches that could have fixed this? I'm willing to do the testing. I just looked up what mainline kernel means. Is there a simpler way to test mainline than compiling my own? (It's been more than 10 years since I last compiled my own Linux kernel.)
Signature · 2 lines
You are receiving this mail because: You are the QA Contact for the bug.
https://bugzilla.samba.org/show_bug.cgi?id=14201
--- Comment #3 from Patrick Böker <[email protected]> --- I have tried this again on a fresh Fedora 36 (Kernel 5.17.5). This test system does not show the described behavior anymore.
Signature · 2 lines
You are receiving this mail because: You are the QA Contact for the bug.
https://bugzilla.samba.org/show_bug.cgi?id=14201
--- Comment #4 from Paulo Alcantara <[email protected]> --- Hi Patrick,
It's OK, no problem :-) Some distros generally have their own packages to easily tests latest kernels in case you don't want to build your own.
There were several DFS related patches since the last version you tested (4.18), so yes, some of them might have fixed your last issue.
Can we close this bug now?
In case you are able to reproduce it again, feel free to reopen it. Thanks.
Signature · 2 lines
You are receiving this mail because: You are the QA Contact for the bug.
https://bugzilla.samba.org/show_bug.cgi?id=14201
Patrick Böker <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED--- Comment #5 from Patrick Böker <[email protected]> --- Works on 5.17.5. So I assume it got fixed in the meantime.
Signature · 2 lines
You are receiving this mail because: You are the QA Contact for the bug.