From: syzbot <syzbot+0c89d865531d053abb2d@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: [syzbot] [ext4?] kernel BUG in ext4_write_inline_data_end (2)
Date: Fri, 02 Feb 2024 01:24:26 -0800 [thread overview]
Message-ID: <000000000000ac258b061062ad8d@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 6764c317b6bb Merge tag 'scsi-fixes' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=132faab7e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=2c0ac5dfae6ecc58
dashboard link: https://syzkaller.appspot.com/bug?extid=0c89d865531d053abb2d
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/90c636d7609b/disk-6764c317.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9d76784c4adc/vmlinux-6764c317.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4fa116a29660/bzImage-6764c317.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+0c89d865531d053abb2d@syzkaller.appspotmail.com
------------[ cut here ]------------
kernel BUG at fs/ext4/inline.c:763!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI
CPU: 1 PID: 11999 Comm: syz-executor.1 Not tainted 6.8.0-rc2-syzkaller-00055-g6764c317b6bb #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
RIP: 0010:ext4_write_inline_data_end+0x550/0xc20 fs/ext4/inline.c:763
Code: 25 28 00 00 00 0f 85 1d 06 00 00 48 81 c4 b0 00 00 00 44 89 f0 5b 5d 41 5c 41 5d 41 5e 41 5f e9 46 d6 87 08 e8 21 65 4c ff 90 <0f> 0b e8 19 65 4c ff 4d 8d 7c 24 34 4c 89 e7 e8 5c 3c 7c ff be 04
RSP: 0018:ffffc90004a3f928 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff8880452c82b0 RCX: ffffffff82400124
RDX: ffff888020358000 RSI: ffffffff8240049f RDI: 0000000000000001
RBP: 0000000000000020 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000004 R12: ffffea00013a6980
R13: 0000000000000020 R14: ffff8880452c8050 R15: ffffc90004a3f978
FS: 00007f1365d136c0(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb7e6f02425 CR3: 0000000028762000 CR4: 0000000000350ef0
Call Trace:
<TASK>
ext4_write_end+0x4af/0xed0 fs/ext4/inode.c:1284
generic_perform_write+0x33b/0x620 mm/filemap.c:3941
ext4_buffered_write_iter+0x11f/0x3d0 fs/ext4/file.c:299
ext4_file_write_iter+0x819/0x1960 fs/ext4/file.c:698
call_write_iter include/linux/fs.h:2085 [inline]
new_sync_write fs/read_write.c:497 [inline]
vfs_write+0x6e1/0x1110 fs/read_write.c:590
ksys_write+0x12f/0x260 fs/read_write.c:643
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xd8/0x270 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x6f/0x77
RIP: 0033:0x7f136507dda9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f1365d130c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f13651abf80 RCX: 00007f136507dda9
RDX: 0000000000000020 RSI: 00000000200002c0 RDI: 0000000000000005
RBP: 00007f13650ca47a R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000000b R14: 00007f13651abf80 R15: 00007ffc77beff18
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:ext4_write_inline_data_end+0x550/0xc20 fs/ext4/inline.c:763
Code: 25 28 00 00 00 0f 85 1d 06 00 00 48 81 c4 b0 00 00 00 44 89 f0 5b 5d 41 5c 41 5d 41 5e 41 5f e9 46 d6 87 08 e8 21 65 4c ff 90 <0f> 0b e8 19 65 4c ff 4d 8d 7c 24 34 4c 89 e7 e8 5c 3c 7c ff be 04
RSP: 0018:ffffc90004a3f928 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff8880452c82b0 RCX: ffffffff82400124
RDX: ffff888020358000 RSI: ffffffff8240049f RDI: 0000000000000001
RBP: 0000000000000020 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000004 R12: ffffea00013a6980
R13: 0000000000000020 R14: ffff8880452c8050 R15: ffffc90004a3f978
FS: 00007f1365d136c0(0000) GS:ffff8880b9500000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffb08627d58 CR3: 0000000028762000 CR4: 0000000000350ef0
---
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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
next reply other threads:[~2024-02-02 9:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 9:24 syzbot [this message]
2024-02-06 22:48 ` [syzbot] [ext4?] kernel BUG in ext4_write_inline_data_end (2) syzbot
2024-11-08 9:16 ` [syzbot] demo123---demo123---0c89d865531d053abb2d syzbot
2024-11-08 10:27 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2024-02-06 15:44 [syzbot] [ext4?] kernel BUG in ext4_write_inline_data_end (2) xingwei lee
[not found] <173105740149.2293654.8622543419878528605@GCRAZCDL0021.westus2.cloudapp.azure.com>
2024-11-08 9:38 ` syzbot
[not found] <173106166139.2299330.8314210328501109966@GCRAZCDL0021.westus2.cloudapp.azure.com>
2024-11-08 10:48 ` 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=000000000000ac258b061062ad8d@google.com \
--to=syzbot+0c89d865531d053abb2d@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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.