From: samba-bugs@samba.org
To: cifs-qa@samba.org
Subject: [Bug 14201] DFS mount does not pass context option to actual share mounts
Date: Tue, 26 Jul 2022 13:15:01 +0000 [thread overview]
Message-ID: <bug-14201-10630-lvZYBgBjtF@https.bugzilla.samba.org/> (raw)
In-Reply-To: <bug-14201-10630@https.bugzilla.samba.org/>
https://bugzilla.samba.org/show_bug.cgi?id=14201
--- Comment #4 from Paulo Alcantara <palcantara@samba.org> ---
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.
--
You are receiving this mail because:
You are the QA Contact for the bug.
next prev parent reply other threads:[~2022-07-26 13:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14201-10630@https.bugzilla.samba.org/>
2022-07-25 16:49 ` [Bug 14201] DFS mount does not pass context option to actual share mounts samba-bugs
2022-07-26 7:29 ` samba-bugs
2022-07-26 12:34 ` samba-bugs
2022-07-26 13:15 ` samba-bugs [this message]
2022-07-26 13:55 ` samba-bugs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-14201-10630-lvZYBgBjtF@https.bugzilla.samba.org/ \
--to=samba-bugs@samba.org \
--cc=cifs-qa@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox