Bug 980324
Summary: | Fedora19: Call Traces while running flail | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | IBM Bug Proxy <bugproxy> | ||||||||
Component: | python | Assignee: | Bohuslav "Slavek" Kabrda <bkabrda> | ||||||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | medium | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 19 | CC: | bkabrda, dmalcolm, ivazqueznet, jkachuck, jonathansteffan, tomspur, wgomerin | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | All | ||||||||||
OS: | All | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2015-02-17 15:46:46 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: | |||||||||||
Attachments: |
|
Description
IBM Bug Proxy
2013-07-02 05:30:42 UTC
Created attachment 767618 [details]
s390x var_log_msgs
Created attachment 767619 [details]
ppc64 var_log_msgs
Huh, why is this assigned to Python? ------- Comment From vaish123.com 2013-07-02 08:05 EDT------- (In reply to comment #7) > Huh, why is this assigned to Python? Sorry, my bad. This has to be directed to security. Created attachment 813314 [details]
dmesg output
------- Comment on attachment From iranna.ankad.com 2013-10-17 12:53 EDT-------
This bug is still reproducible in Fedora20 Alpha.
FYI,
[root@oc4352187340 bugs]# sysctl -n vm.min_free_kbytes
67584
[root@oc4352187340 bugs]# uname -a
Linux oc4352187340.ibm.com 2.6.32-279.19.1.el6.x86_64 #1 SMP Wed Nov 28 19:02:25 CET 2012 x86_64 x86_64 x86_64 GNU/Linux
[root@oc4352187340 bugs]#
Note: attaching fresh dmesg output taken while running flail test
------- Comment From iranna.ankad.com 2013-10-17 13:02 EDT------- (In reply to comment #9) > Created attachment 82823 [details] > dmesg output > This bug is still reproducible in Fedora20 Alpha. > FYI, > [root@oc4352187340 bugs]# sysctl -n vm.min_free_kbytes > 67584 > [root@oc4352187340 bugs]# uname -a > Linux oc4352187340.ibm.com 2.6.32-279.19.1.el6.x86_64 #1 SMP Wed Nov 28 > 19:02:25 CET 2012 x86_64 x86_64 x86_64 GNU/Linux > [root@oc4352187340 bugs]# Please ignore o/p of above two commands, I realised that by mistake I ran them on my RH6.3 Thinkpad. Here is the correct o/p from test system. [root@ test]# uname -a Linux 3.11.0-300.fc20.ppc64p7 #1 SMP Thu Sep 5 16:13:50 MST 2013 ppc64 ppc64 ppc64 GNU/Linux [root@ test]# sysctl -n vm.min_free_kbytes 28930 [root@ test]# ------- Comment From gusld.com 2013-10-22 19:08 EDT------- This bug is very confusing. I could not understand what is being asked here. The only call traces I could find in the logs are either flail segfaulting or the kernel complaining it could not complete a request to allocate several terabytes of memory. There is clearly nothing wrong about the kernel call traces. Regarding the flail segfaults, flail is not part of Fedora, so this should be handled somewhere else other than the Fedora bugzilla. Can we close this bug? ------- Comment From iranna.ankad.com 2013-11-16 20:11 EDT------- (In reply to comment #13) > This bug is very confusing. I could not understand what is being asked here. > The only call traces I could find in the logs are either flail segfaulting > or the kernel complaining it could not complete a request to allocate > several terabytes of memory. > There is clearly nothing wrong about the kernel call traces. Regarding the > flail segfaults, flail is not part of Fedora, so this should be handled > somewhere else other than the Fedora bugzilla. > Can we close this bug? Hello Gustavo, Though I could recreate this bug even in F20 beta, sort of I agree that above call traces give any sense of something wrong happening here. Even I wonder why vmalloc is trying to allocate tera bytes of memory. Still..I tried to rerun flail test by increasing the allocation capacity of vmalloc to 7TB (70368000M in this case) and also tried setting the vm.min_free_kbytes to 1.6 TB. Nothing ..helped, above errors are still recreating. Since flail is a system call security fuzzing test case, I would mainly look out for any system crash or kernel oops out of this test, so I am not much worried about above errors. I am OK to close this for now. Thanks! [root@als0153 ~]# cat /proc/cmdline BOOT_IMAGE=/vmlinuz-3.11.6-301.fc20.ppc64p7 root=UUID=be312012-4d7f-442e-8a02-7de8bb0e4323 ro vconsole.keymap=us vconsole.font=latarcyrheb-sun16 LANG=en_US.UTF-8 vmalloc=70368000M [root@als0153 ~]# sysctl -n vm.min_free_kbytes 16354000 ------- Comment From vaish123.com 2013-11-18 06:18 EDT------- (In reply to comment #13) > This bug is very confusing. I could not understand what is being asked here. > The only call traces I could find in the logs are either flail segfaulting > or the kernel complaining it could not complete a request to allocate > several terabytes of memory. > There is clearly nothing wrong about the kernel call traces. Regarding the > flail segfaults, flail is not part of Fedora, so this should be handled > somewhere else other than the Fedora bugzilla. > Can we close this bug? -- Closing the bug on the IBM side -- This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |