Bug 725212

Summary: [ext4/xfstests 075] kernel panic on xfstests 075 run with 2048/1024 block size
Product: Red Hat Enterprise Linux 6 Reporter: Eryu Guan <eguan>
Component: kernelAssignee: Eric Sandeen <esandeen>
Status: CLOSED DUPLICATE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: esandeen, lczerner, rwheeler
Target Milestone: rc   
Target Release: 6.2   
Hardware: s390x   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-31 22:49:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Eryu Guan 2011-07-24 08:24:45 UTC
Description of problem:
xfstests 075 makes ext4 panic on s390x host, this only happens with 2048 or 1024 block size, 4096 block size can pass the test

ext3 doesn't have this issue(4096&2048&1024 block size)

Version-Release number of selected component (if applicable):
I tried the following kernels:
kernel-2.6.32-71.el6
kernel-2.6.32-131.0.15.el6
kernel-2.6.32-131.6.1.el6
kernel-2.6.32-171.el6
So not a regression

How reproducible:
100%

Steps to Reproduce:
1. yum install rh-tests-kernel-filesystems-xfs-xfstests -y
2. cd /mnt/tests/kernel/filesystems/xfs/xfstests; ./install_all.sh
3. TEST_PARAM_FSTYPE=ext4 TEST_PARAM_RUNTESTS=075 TEST_PARAM_BLKSIZE=2048 make run
  
Actual results:
Process fsx (pid: 2899, task: 000000001d000b90, ksp: 0000000001747360)
0000000001747578 00000000017474f8 0000000000000002 0000000000000000
       0000000001747598 0000000001747510 0000000001747510 00000000004be880
       0000000000000011 0000000000000000 0000000000000006 0000000000000008
       000000000000000d 000000000000000c 0000000001747568 0000000000000000
       0000000000000000 000000000010512c 00000000017474f8 0000000001747538
Call Trace:
(Ý<000000000010502c>¨ show_trace+0xe8/0x138)
 Ý<00000000004be6c2>¨ panic+0x92/0x1fc
 Ý<000000000010567e>¨ die+0x16e/0x17c
 Ý<0000000000106ef6>¨ illegal_op+0x1f2/0x1f8
 Ý<00000000001185dc>¨ pgm_exit+0x0/0x4
 Ý<000003c0009858da>¨ mpage_put_bnr_to_bhs+0x382/0x3c8 Ýext4¨
(Ý<000003c000985636>¨ mpage_put_bnr_to_bhs+0xde/0x3c8 Ýext4¨)
 Ý<000003c000987e2c>¨ mpage_da_map_blocks+0x1c0/0x440 Ýext4¨
 Ý<000003c00098812c>¨ mpage_add_bh_to_extent+0x80/0x128 Ýext4¨
 Ý<000003c0009885ac>¨ write_cache_pages_da+0x3d8/0x4b4 Ýext4¨
 Ý<000003c0009889be>¨ ext4_da_writepages+0x336/0x718 Ýext4¨
 Ý<00000000001ef67e>¨ __filemap_fdatawrite_range+0x6e/0x7c
 Ý<000003c00097de6c>¨ ext4_release_file+0xa4/0xfc Ýext4¨
 Ý<000000000025338e>¨ __fput+0xf6/0x238
 Ý<000000000024f29a>¨ filp_close+0x72/0xa0
 Ý<000000000024f3b0>¨ SyS_close+0xe8/0x14c
 Ý<0000000000118444>¨ sysc_tracego+0xe/0x14
 Ý<00000200000504f0>¨ 0x200000504f0
01: HCPGIR450W CP entered; disabled wait PSW 00020001 80000000 00000000 00111ED0

Expected results:
No panic, test pass

Additional info:
This seems related to bug 692530, not sure whether they share the same root cause

Comment 2 Eryu Guan 2011-08-16 10:09:31 UTC
112 is based on 075 and can also lead to this panic.

Comment 3 RHEL Program Management 2011-10-07 15:42:16 UTC
Since RHEL 6.2 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.