From: Tasmiya Nalatwad <tasmiya@linux.vnet.ibm.com>
To: linux-block@vger.kernel.org
Cc: axboe@kernel.dk, kch@nvidia.com, martin.petersen@oracle.com,
mputtash@linux.vnet.com, linux-kernel@vger.kernel.org,
sachinp@linux.vnet.com, abdhaleem@linux.vnet.ibm.com,
linuxppc-dev@lists.ozlabs.org, hch@lst.de
Subject: [linux-next] [FC/EXT4] [PPC] WARNING: CPU: 33 PID: 47869 at block/blk-lib.c:50 __blkdev_issue_discard+0x250/0x280
Date: Tue, 10 May 2022 16:27:15 +0530 [thread overview]
Message-ID: <b6e58d90-a0e4-00bb-7d61-487f163c8b8b@linux.vnet.ibm.com> (raw)
Greetings,
linux-next kernel 5.18.0-rc5-next-20220506 WARN_ON is triggered while
running stress test on FC disk created with the EXT4 filesystem.
Console Logs :
md127: detected capacity change from 0 to 62879744
EXT4-fs (dm-11): mounted filesystem with ordered data mode. Quota
mode: none.
md127: detected capacity change from 62879744 to 0
md: md127 stopped.
EXT4-fs (dm-11): mounted filesystem with ordered data mode. Quota
mode: none.
md127: detected capacity change from 0 to 62879744
WARNING: CPU: 33 PID: 47869 at block/blk-lib.c:50
__blkdev_issue_discard+0x250/0x280
Modules linked in: raid0 rpadlpar_io rpaphp nfnetlink tcp_diag
udp_diag inet_diag unix_diag af_packet_diag netlink_diag bonding rfkill
sunrpc pseries_rng xts vmx_crypto gf128mul sch_fq_codel binfmt_misc
ip_tables ext4 mbcache jbd2 dm_round_robin sd_mod t10_pi crc64_rocksoft
crc64 sg ibmvfc scsi_transport_fc ibmveth dm_multipath dm_mirror
dm_region_hash dm_log dm_mod fuse
CPU: 33 PID: 47869 Comm: mkfs.ext4 Kdump: loaded Not tainted
5.18.0-rc5-next-20220506-autotest #1
NIP: c00000000064beb0 LR: c00000000064bf40 CTR: 0000000000000000
REGS: c0000000a7a2f870 TRAP: 0700 Not tainted
(5.18.0-rc5-next-20220506-autotest)
MSR: 8000000000029033 <SF,EE,ME,IR,DR,RI,LE> CR: 28002282 XER: 00000000
CFAR: c00000000064bd24 IRQMASK: 0
GPR00: c00000000064bf40 c0000000a7a2fb10 c0000000028cbd00
c0000000ed960000
GPR04: 0000000000000000 0000000000008000 0000000000000cc0
c0000000a7a2fc28
GPR08: 0000000000000000 c0000000c70a0000 00000000ffffffff
0000000000000000
GPR12: 0000000000002000 c0000018ff95ee80 0000000000000000
0000000000000000
GPR16: 0000000000000000 0000000000000000 000000000077ef00
000000014e1e56a0
GPR20: 0000000000008000 00007fff988b0588 00007ffff213dfe8
0000000000000000
GPR24: 0000000000000003 0000000000000000 0000000001000000
c0000000ed960000
GPR28: 0000000001000000 0000000000000000 c0000000ed960000
c0000000ed960000
NIP [c00000000064beb0] __blkdev_issue_discard+0x250/0x280
LR [c00000000064bf40] blkdev_issue_discard+0x60/0xe0
Call Trace:
[c0000000a7a2fb10] [c0000000a7a2fb60] 0xc0000000a7a2fb60 (unreliable)
[c0000000a7a2fbe0] [c00000000064bf40] blkdev_issue_discard+0x60/0xe0
[c0000000a7a2fc70] [c00000000065e840] blkdev_common_ioctl+0x1b0/0xbf0
[c0000000a7a2fd00] [c00000000065f6a8] blkdev_ioctl+0x428/0x6e0
[c0000000a7a2fd60] [c0000000004857c8] sys_ioctl+0xf8/0x150
[c0000000a7a2fdb0] [c00000000002f468] system_call_exception+0x178/0x380
[c0000000a7a2fe10] [c00000000000c64c] system_call_common+0xec/0x250
--- interrupt: c00 at 0x7fff98524480
NIP: 00007fff98524480 LR: 00007fff98867828 CTR: 0000000000000000
REGS: c0000000a7a2fe80 TRAP: 0c00 Not tainted
(5.18.0-rc5-next-20220506-autotest)
MSR: 800000000280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR:
24002288 XER: 00000000
IRQMASK: 0
GPR00: 0000000000000036 00007ffff213dec0 00007fff98617100
0000000000000003
GPR04: 0000000020001277 00007ffff213df48 0000000001000000
0000000000001000
GPR08: 0000000000000003 0000000000000000 0000000000000000
0000000000000000
GPR12: 0000000000000000 00007fff9895ce40 0000000000000000
0000000000000000
GPR16: 0000000000000000 0000000000000000 000000000077ef00
000000014e1e56a0
GPR20: 0000000000008000 00007fff988b0588 00007ffff213dfe8
0000000000000000
GPR24: 000000011b2a0890 000000011b2a08a0 000000011b2a0880
000000011b2a00d8
GPR28: 0000000000000000 00007fff988b0590 000000011b2a00e0
00007ffff213e0a0
NIP [00007fff98524480] 0x7fff98524480
LR [00007fff98867828] 0x7fff98867828
--- interrupt: c00
Instruction dump:
60000000 2fa30000 419e0018 3c62fe6e 38810068 38630da0 4bb95b21 60000000
3b20ffa1 4bffff60 60000000 60000000 <0fe00000> 7c0802a6 fb010090 fb4100a0
---[ end trace 0000000000000000 ]---
--
Regards,
Tasmiya Nalatwad
IBM Linux Technology Center
reply other threads:[~2022-05-10 11:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b6e58d90-a0e4-00bb-7d61-487f163c8b8b@linux.vnet.ibm.com \
--to=tasmiya@linux.vnet.ibm.com \
--cc=abdhaleem@linux.vnet.ibm.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=martin.petersen@oracle.com \
--cc=mputtash@linux.vnet.com \
--cc=sachinp@linux.vnet.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).