Bug 745436
| Summary: | missing warn_on() in 'Call Trace's | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Nikola Pajkovsky <npajkovs> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | anton, dhoward, dvlasenk, gansalmon, iprikryl, itamar, jmoskovc, jonathan, kernel-maint, kklic, madhu.chinakonda, mads, mtoman, npajkovs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 728194 | Environment: | |
| Last Closed: | 2011-11-08 00:46:45 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 728194 | ||
| Bug Blocks: | |||
|
Description
Nikola Pajkovsky
2011-10-12 11:12:29 UTC
Moving this discussion to rawhide. It's likely to not be fixed in f16, as this is really an upstream issue. That traceback is because the function calls dump_stack instead of WARN_ON or BUG_ON. There are numerous places in the kernel that just call dump_stack for various reasons. Moving the "------------[ cut here ]------------\n" inside of dump_stack isn't really feasible either, because often other information is desired in the cut portion that dump_stack doesn't provide (like the list of modules, or a register dump, or some other informational message). I think we're going to close this out as CANTFIX because there doesn't really seem to be a suitable all-around solution for the various usages. What do you recommend abrt should do? How can it generate reports that is (slightly) useful for you as kernel guy? Should it just add handling of new kinds of traces as they are reported incorrectly? And perhaps fall back to report 20 lines before an unknown "Call Trace:"? I assume there is a kind of a privacy issue here and it thus can't report too much of the log automatically. I discussed it with another kernel developer and I was told that if there is no "BUG: " or "WARNING: " or other known oops delimiter we (ABRT) should just ignore it. It seems strange that the kernel should emit stack traces as a part of its normal operation. I would assume that it implied that something should be fixed. Ok, there is no reason to report a 'initrd not found' trace, but I guess that is a strange exception. |