There have been several people on the mailing lists asking why mounting with sec=krb5 doesn't work when they are using alternate credcaches. Let's fix this proactively by backporting commit 704b739 to 3.3 and 3.4. That'll also mean pulling back a series of preliminary patches as well but that's probably for the best anyway.
Looking at this... It's probably easier and safer to basically move the cifs.upcall.c in both branches to the latest version. There aren't that many commits we can leave behind when we fix this, so we might as well take them all.
Created attachment 4843 [details] tarball containing patches to update cifs.upcall in v3-3-test and v3-4-test This tarball contains 12 patches for each branch that should bring cifs.upcall in that branch close to the one in the master branch. I've given both a basic smoke testing and they seem to be OK. I think bringing them into the next set of v3.3 and v3.4 releases is reasonable. Many people want to use CIFS sec=krb5 in conjunction with pam_krb5 (which tends to put the credcache in an alternate location).
I requested review by Steve, but if anyone else wants to ACK it that would be fine too.
Sorry Jeff, there are way too many patches to review for 3.3.9 (due to *ship* tomorrow). Code freeze for 3.4.3 is tomorrow also. Wish you'd have brought this up a couple of weeks ago. Jeremy.
reviewed
Comment on attachment 4843 [details] tarball containing patches to update cifs.upcall in v3-3-test and v3-4-test I believe Steve meant to check the review + on the tarball here...
Reassigning to Karolin. Let me know if there's anything further I need to do here.
Pushed to v3-4-test and v3-3-test. Closing out bug report. Thanks!