From: Alexander Koch <mail@alexanderkoch.net>
To: linux-cifs@vger.kernel.org
Subject: cifs.upcall broken with cifs-utils 6.13
Date: Tue, 20 Apr 2021 18:05:20 +0200 [thread overview]
Message-ID: <a01d5d22-5990-c00d-bc2a-582d2585ea69@alexanderkoch.net> (raw)
The recent release of cifs-utils 6.13, more precisely e461afd8cf (which,
to my understanding, is a fix for CVE-2021-20208) makes attempts of
mounting CIFS shares with krb5 fail for me:
cifs.upcall[78171]: switch_to_process_ns: setns() failed for cgroup
cifs.upcall[78171]: unable to switch to process namespace:
Operation not permitted
Can anyone tell me if this is a packaging/configuration issue (Arch in
my case) or a bug?
Full mount log can be found in [1], along with a confirmation of the
observed behaviour from another user.
Thanks!
Best regards,
Alex
[1]
https://www.reddit.com/r/archlinux/comments/mukvv6/cifs_mount_broken_again_with_cifsutils6131/
next reply other threads:[~2021-04-20 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 16:05 Alexander Koch [this message]
2021-04-20 16:41 ` cifs.upcall broken with cifs-utils 6.13 Aurélien Aptel
2021-04-20 17:02 ` Alexander Koch
2021-08-06 7:09 ` Alexander Koch
2021-08-06 9:02 ` Pavel Shilovsky
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=a01d5d22-5990-c00d-bc2a-582d2585ea69@alexanderkoch.net \
--to=mail@alexanderkoch.net \
--cc=linux-cifs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).