From: syzbot <syzbot+80d413b5e0bdc4e192ba@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: [syzbot] WARNING in ext4_evict_inode (2)
Date: Wed, 15 Sep 2021 09:40:26 -0700 [thread overview]
Message-ID: <000000000000f3aadf05cc0b5a3d@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 08dad2f4d541 net: stmmac: allow CSR clock of 300MHz
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=159f1853300000
kernel config: https://syzkaller.appspot.com/x/.config?x=16e23f04679ec35e
dashboard link: https://syzkaller.appspot.com/bug?extid=80d413b5e0bdc4e192ba
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+80d413b5e0bdc4e192ba@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 9028 at fs/ext4/inode.c:230 ext4_evict_inode+0xf9a/0x1950 fs/ext4/inode.c:230
Modules linked in:
CPU: 1 PID: 9028 Comm: syz-executor.5 Not tainted 5.14.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:ext4_evict_inode+0xf9a/0x1950 fs/ext4/inode.c:230
Code: 28 41 bc 01 00 00 00 48 89 04 24 e9 60 f6 ff ff c7 44 24 24 06 00 00 00 c7 44 24 20 06 00 00 00 e9 df f6 ff ff e8 56 ad 62 ff <0f> 0b e9 c6 f5 ff ff e8 7a ee a9 ff e9 60 f1 ff ff 48 89 cf e8 6d
RSP: 0018:ffffc90000f2fca0 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 1ffff920001e5f9a RCX: 0000000000000000
RDX: ffff88807ef11c80 RSI: ffffffff8213640a RDI: 0000000000000003
RBP: ffff888042a282a0 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff821359ce R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000001 R14: ffff88814050ab60 R15: ffff8880414e4038
FS: 000000000230a400(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b32643000 CR3: 000000005087c000 CR4: 00000000001506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
evict+0x2ed/0x6b0 fs/inode.c:586
iput_final fs/inode.c:1662 [inline]
iput.part.0+0x539/0x850 fs/inode.c:1688
iput+0x58/0x70 fs/inode.c:1678
do_unlinkat+0x418/0x650 fs/namei.c:4176
__do_sys_unlink fs/namei.c:4217 [inline]
__se_sys_unlink fs/namei.c:4215 [inline]
__x64_sys_unlink+0xc6/0x110 fs/namei.c:4215
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x465f37
Code: 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 57 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd277ea528 EFLAGS: 00000206 ORIG_RAX: 0000000000000057
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 0000000000465f37
RDX: 00007ffd277ea560 RSI: 00007ffd277ea560 RDI: 00007ffd277ea5f0
RBP: 00007ffd277ea5f0 R08: 0000000000000001 R09: 00007ffd277ea3c0
R10: 000000000230b89b R11: 0000000000000206 R12: 00000000004bee90
R13: 00007ffd277eb6c0 R14: 000000000230b810 R15: 00007ffd277eb700
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
reply other threads:[~2021-09-15 16:40 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=000000000000f3aadf05cc0b5a3d@google.com \
--to=syzbot+80d413b5e0bdc4e192ba@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.