Bug 745180

Summary: Trinity syscall fuzzer appears to be able to wedge IO subsystem on ppc
Product: Red Hat Enterprise Linux 6 Reporter: Mike Gahagan <mgahagan>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED WONTFIX QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: jburke, sbest
Target Milestone: rc   
Target Release: 6.3   
Hardware: ppc64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-06 10:59:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 767187    

Description Mike Gahagan 2011-10-11 14:59:29 UTC 
Description of problem:
System stopped responding during automated trinity syscall fuzzer test, appears the IO subsystem got wedged with call traces in the form:

INFO: task jbd2/dm-0-8:667 blocked for more than 120 seconds. 
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 
jbd2/dm-0-8   D 0000000000000000     0   667      2 0x00008000 
Call Trace: 
[c000000171cf32d0] [c000000171cf3380] 0xc000000171cf3380 (unreliable) 
[c000000171cf34a0] [c0000000000142c8] .__switch_to+0xf8/0x1d0 
[c000000171cf3530] [c0000000005aa294] .schedule+0x404/0xd70 
[c000000171cf3830] [c0000000005aac90] .io_schedule+0x90/0x110 
[c000000171cf38c0] [c00000000014eea0] .sync_page+0x70/0xa0 
[c000000171cf3940] [c0000000005ab9b4] .__wait_on_bit+0xb4/0x130 
[c000000171cf39f0] [c00000000014f1bc] .wait_on_page_bit+0x7c/0xa0 
[c000000171cf3ab0] [c000000000150290] .wait_on_page_writeback_range+0x120/0x200 
[c000000171cf3c10] [d0000000023b3dc8] .jbd2_journal_commit_transaction+0x848/0x1910 [jbd2] 
[c000000171cf3de0] [d0000000023bc28c] .kjournald2+0xec/0x300 [jbd2] 
[c000000171cf3ed0] [c0000000000bca9c] .kthread+0xbc/0xd0 
[c000000171cf3f90] [c000000000032034] .kernel_thread+0x54/0x70 
INFO: task trinity:23986 blocked for more than 120 seconds. 
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 
trinity       D 000000806ff1f184     0 23986  26841 0x00008082 
Call Trace: 
[c00000017a857580] [c00000017a857630] 0xc00000017a857630 (unreliable) 
[c00000017a857750] [c0000000000142c8] .__switch_to+0xf8/0x1d0 
[c00000017a8577e0] [c0000000005aa294] .schedule+0x404/0xd70 
[c00000017a857ae0] [d0000000023bbd04] .jbd2_log_wait_commit+0xe4/0x1d0 [jbd2] 
[c00000017a857bd0] [d0000000024f2ca0] .ext4_sync_file+0x1a0/0x2f0 [ext4] 
[c00000017a857c80] [c0000000001fb694] .vfs_fsync_range+0xd4/0x130 
[c00000017a857d30] [c0000000001fb7ac] .do_fsync+0x3c/0x70 
[c00000017a857dc0] [c0000000001fb828] .SyS_fsync+0x18/0x30 
[c00000017a857e30] [c000000000008564] syscall_exit+0x0/0x40 


Version-Release number of selected component (if applicable):
1005.1 tree, -206 kernel (snap 1)

How reproducible:
only observed once so far

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Random seed in use: 0xb2999840
Comment 3 RHEL Program Management 2012-05-03 04:52:27 UTC 
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 4 Jan Kurik 2017-12-06 10:59:42 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/