Bug 1037793
| Summary: | Missing info file in dummy gssd entry in rpc_pipefs | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | nmorey <nicolas> |
| Component: | kernel | Assignee: | Steve Dickson <steved> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | bastian_knight, bfields, gansalmon, itamar, jlayton, jonathan, kernel-maint, luc.lalonde, madhu.chinakonda, steved |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | kernel-3.12.6-200.fc19 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-01-03 08:31:59 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
nmorey
2013-12-03 20:03:40 UTC
Moving to nfs-utils for now. Steve and Jeff asked us to add those patches to the kernel. Makes sense. We could certainly fix it with a kernel patch that adds a dummy "info" file, but...ick. Maybe it'd be best to just make gssd silence these ERROR messages by default. They aren't particularly helpful, IMO... Steve, thoughts? Ok I sent out a patch for it this morning. We'll see what Trond says:
http://marc.info/?l=linux-nfs&m=138624689302466&w=2
...we'll probably also want to take this patch:
http://marc.info/?l=linux-nfs&m=138624684502447&w=2
...and I'm working on a 3rd patch to fix some leaks that can happen when the mount of rpc_pipefs fails due to the notifier failing.
This is now fixed in the latest f20 kernel release. Er... it is? We didn't bring any of the patches Jeff mentioned in comment #3 into the kernel. Can you point to the Fedora kernel commit that fixed it? (In reply to Josh Boyer from comment #5) > Er... it is? We didn't bring any of the patches Jeff mentioned in comment > #3 into the kernel. Can you point to the Fedora kernel commit that fixed it? My bad... I updated my f19 kernel to 3.11.10-200.fc19 and it appeared the 15 second delay was gone, so I just assumed they went into F20 as well... Reopening... (In reply to Steve Dickson from comment #6) > (In reply to Josh Boyer from comment #5) > > Er... it is? We didn't bring any of the patches Jeff mentioned in comment > > #3 into the kernel. Can you point to the Fedora kernel commit that fixed it? > My bad... I updated my f19 kernel to 3.11.10-200.fc19 and it > appeared the 15 second delay was gone, so I just assumed > they went into F20 as well... We added the patches to get rid of the 15 second delay in all releases, so you're correct there. This bug is tracking some fallout of adding those patches though. Here is the upstream patch that will mostly like fix this problem http://marc.info/?l=linux-nfs&m=138659989103371&w=2 Also changing the component from nfs-utils to kernel. Jeff, do you think we need all 3 patches here? Yeah, I think that would be best. Could someone test this scratch build when it completes and see if the issue is sufficiently resolved? http://koji.fedoraproject.org/koji/taskinfo?taskID=6276121 I'd like to get confirmation before I commit the patches. I have the same problem. I have tested kernels: kernel-3.11.10-301.3.fc20.src.rpm from above address and kernel-3.12.5-301.fc20.x86_64 from updates testing. The 3.11.10-301.3.fc20 gets rid of the error message but kerberos authentication fail with any kernel with access denied message for NFS4 exported share. The share worked without problems in FC 19. I tested kernel-3.11.10-301.3.fc20.x86_64 on a F19 system and it solves the problem for me... The last known kernel that worked properly for me is: kernel-3.11.6-200.fc19.x86_64 However, after updating to latest F19 kernel (kernel-3.11.10-200.fc19.x86_64) I get the above GSSD error messages and am unable to initiate an NFSv4 kerberos mount. I'll be sticking with kernel-3.11.6-200.fc19.x86_64 for now until a fix filters down to F19. Strange....I seem to be able to mount with sec=krb5 with 3.11.10-301.3.fc20.x86_64+debug just fine. My client is a rawhide box though, so maybe the nfs-utils differences are making a difference there. I'll see if I can roll up a f19 VM and do some testing with it. Ok, I set up an f19 VM and patched to current updates. Installed the kernel from comment #11. When I first booted, I wasn't able to mount either, but that was because rpc.gssd wasn't running. Once I started it, it worked fine. Can you confirm whether gssd was running on your system after booting to the new kernel? Yes. gssd (started by nfs-secure.service) is running on my system and I get "Permission denied" message. ...and if you just boot to the older kernel w/o changing anything else. Does it work just fine then? What nfs-utils version do you have? ...and to be clear, what's the latest kernel version that does work for you? I have currently nfs-utils-1.2.8-6.0.fc20.x86_64. The kerberized share worked correctly on Feedora 19. After upgrading to F20 none of the kernel versions allows me to access the share (initial one after upgrade, the one from comment 11 and the one from updates testing). To be clear the share is still accessible on F19 boxes. I had some similar problems after upgrading to fc20. HoweverI cannot say if its due to fc 20. I've been upgrading since fc14 and had some very old config files. I tried to use the rpmnew ones and it all went haywire. After a couple of hours playing with old and new ones it got working again, At leat from a fresh install nfs4+krb seems ok according to my IT guy. (In reply to Michal Piotrowski from comment #19) > I have currently nfs-utils-1.2.8-6.0.fc20.x86_64. > > The kerberized share worked correctly on Feedora 19. After upgrading to F20 > none of the kernel versions allows me to access the share (initial one after > upgrade, the one from comment 11 and the one from updates testing). > > To be clear the share is still accessible on F19 boxes. I'm afraid that doesn't tell me anything helpful. You'll likely need to do some debugging to figure out why it isn't working for you and open a new bug if it turns out to be one. I suspect however that that is not at all related to what this bug is about (which is spurious warnings in the logs). (In reply to Josh Boyer from comment #11) > Could someone test this scratch build when it completes and see if the issue > is sufficiently resolved? > > http://koji.fedoraproject.org/koji/taskinfo?taskID=6276121 > > I'd like to get confirmation before I commit the patches. As best I can tell, the ERROR: messages originally reported go away with this kernel. I think you should go ahead and merge these for the next f19/f20 kernels. FWIW, it looks like the upstream patches are probably going to make 3.14. (In reply to Jeff Layton from comment #22) > (In reply to Josh Boyer from comment #11) > > Could someone test this scratch build when it completes and see if the issue > > is sufficiently resolved? > > > > http://koji.fedoraproject.org/koji/taskinfo?taskID=6276121 > > > > I'd like to get confirmation before I commit the patches. > > As best I can tell, the ERROR: messages originally reported go away with > this kernel. I think you should go ahead and merge these for the next > f19/f20 kernels. FWIW, it looks like the upstream patches are probably going > to make 3.14. OK, I'll add them. They'll be on top of 3.12.y at this point, but I don't believe that will matter. OK, added them to F19 and F20, and added these 3 and the 3 for fixing the 15sec hang to rawhide since none of them will land until 3.14. kernel-3.12.6-300.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/kernel-3.12.6-300.fc20 kernel-3.12.6-200.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/kernel-3.12.6-200.fc19 Package kernel-3.12.6-200.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.12.6-200.fc19' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-23935/kernel-3.12.6-200.fc19 then log in and leave karma (feedback). kernel-3.12.6-300.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report. kernel-3.12.6-200.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. |