From: syzbot <syzbot+d43f346675e449548021@syzkaller.appspotmail.com>
To: axboe@kernel.dk, bvanassche@acm.org, jlayton@kernel.org,
linux-kernel@vger.kernel.org, reiserfs-devel@vger.kernel.org,
song@kernel.org, syzkaller-bugs@googlegroups.com,
willy@infradead.org, yi.zhang@huawei.com
Subject: [syzbot] WARNING in journal_end
Date: Tue, 29 Nov 2022 05:49:37 -0800 [thread overview]
Message-ID: <00000000000043463e05ee9c4277@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 9e46a7996732 Add linux-next specific files for 20221125
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12c4ff75880000
kernel config: https://syzkaller.appspot.com/x/.config?x=11e19c740a0b2926
dashboard link: https://syzkaller.appspot.com/bug?extid=d43f346675e449548021
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/758d818cf966/disk-9e46a799.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f7c8696b40a5/vmlinux-9e46a799.xz
kernel image: https://storage.googleapis.com/syzbot-assets/810f9750b87f/bzImage-9e46a799.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d43f346675e449548021@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 28237 at fs/reiserfs/journal.c:3395 journal_end+0x2da/0x330 fs/reiserfs/journal.c:3395
Modules linked in:
CPU: 0 PID: 28237 Comm: syz-executor.0 Not tainted 6.1.0-rc6-next-20221125-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:journal_end+0x2da/0x330 fs/reiserfs/journal.c:3395
Code: ff 4c 89 e7 e8 17 80 b5 ff e9 c0 fd ff ff 4c 89 e7 e8 aa 80 b5 ff e9 01 ff ff ff e8 00 80 b5 ff e9 3a ff ff ff e8 36 5e 67 ff <0f> 0b 41 bc fb ff ff ff e9 ef fe ff ff e8 04 80 b5 ff e9 4c fd ff
RSP: 0018:ffffc9000367fb40 EFLAGS: 00010212
RAX: 0000000000029f05 RBX: 0000000000000000 RCX: ffffc9000f945000
RDX: 0000000000040000 RSI: ffffffff82196b8a RDI: 0000000000000005
RBP: ffffc9000367fbb8 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffffc9000367fbcc
R13: 0000000000000001 R14: ffff888072d58ef8 R15: ffffc9000367fbb8
FS: 00007f6730b9f700(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555557391848 CR3: 00000000175c7000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
reiserfs_truncate_file+0x1c0/0xee0 fs/reiserfs/inode.c:2311
reiserfs_setattr+0xed3/0x1460 fs/reiserfs/inode.c:3395
notify_change+0xca7/0x1420 fs/attr.c:482
do_truncate+0x143/0x200 fs/open.c:65
do_sys_ftruncate+0x51f/0x710 fs/open.c:193
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f672fe8c0d9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f6730b9f168 EFLAGS: 00000246 ORIG_RAX: 000000000000004d
RAX: ffffffffffffffda RBX: 00007f672ffac120 RCX: 00007f672fe8c0d9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000004
RBP: 00007f672fee7ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffe43a9deef R14: 00007f6730b9f300 R15: 0000000000022000
</TASK>
---
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.
next reply other threads:[~2022-11-29 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 13:49 syzbot [this message]
2022-12-03 18:34 ` [syzbot] WARNING in journal_end syzbot
2022-12-05 7:50 ` syzbot
2024-03-06 19:55 ` [syzbot] [reiserfs?] " syzbot
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=00000000000043463e05ee9c4277@google.com \
--to=syzbot+d43f346675e449548021@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=song@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.org \
--cc=yi.zhang@huawei.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 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.