Bug 910457
| Summary: | kernel BUG at net/sunrpc/svc_xprt.c:921! | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jason Tibbitts <j> | ||||||||
| Component: | kernel | Assignee: | nfs-maint | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 18 | CC: | 29551030, bfields, gansalmon, horsley1953, itamar, jonathan, kernel-maint, madhu.chinakonda, schaiba | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-02-18 15:10:41 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: | |||||||||||
| Attachments: |
|
||||||||||
I can't find much on this issue besides this thread from a few weeks ago: http://www.gossamer-threads.com/lists/linux/kernel/1662203 Hmm, got a different backtrace in the sunrpc code on the same machine under what appears to be the same conditions. Will attach that one as well, but if someone would prefer that in a separate ticket, I can do that as well. Created attachment 697332 [details]
A different backtrace received under the same conditions
Created attachment 697374 [details]
fix rpc service shutdown races
Would it be possible to confirm whether the attached fixes the problem?
Let me build a kernel and see. It isn't something I cam immediately reproduce but I'll give it a shot. Thanks! Any results would be helpful, even only "I ran with it for a day and haven't seen the problem again yet." OK, I've finished building and installing a patched kernel. It boots and nfs seems to work OK, so nothing's gotten obviously worse. Previous kernels didn't last for a day, so if things are OK tomorrow then I'll let you know. Well, the machine survived the night; no problems with NFS or otherwise seem to have cropped up. For grins I ran mount;ls;umount in a tight loop and had no issues. I'll keep playing with this kernel for a while, but at this point I'm not sure what else I can do to help get this patch accepted upstream. If there's any kind of additional testing I can do, please let me know. *** This bug has been marked as a duplicate of bug 904870 *** *** Bug 911958 has been marked as a duplicate of this bug. *** *** Bug 908451 has been marked as a duplicate of this bug. *** |
Created attachment 696581 [details] backtrace On a relatively minimal F18 install that has a few automounted directories, including one accessed once an hour, I received the attached backtrace. This happened at pretty much exactly when the machine would have automounted that directory. Afterwards, NFS is dead; nothing is currently mounted but any attempt to mount anything, either directly via calling mount or via autofs simply hangs. This is fully updated F18: kernel-3.7.6-201.fc18.x86_64 nfs-utils-1.2.7-3.fc18.x86_64 autofs-5.0.7-9.fc18.x86_64 I can't easily reproduce this; I don't have a lot of hardware running F18 but another machine with the same basic NFS access patterns hasn't had this issue yet. The machine with the problem had been up for less than five hours and had successfully mounted this directory five times since it was booted. I will reboot to get the machine working again and update this ticket if the problem reoccurs.