From: syzbot <syzbot+158be45e4d99232e1900@syzkaller.appspotmail.com>
To: konishi.ryusuke@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [nilfs?] WARNING in nilfs_btree_assign (3)
Date: Tue, 14 Jan 2025 02:51:03 -0800 [thread overview]
Message-ID: <67864197.050a0220.216c54.0072.GAE@google.com> (raw)
In-Reply-To: <20250114.193428.1276660241787527867.konishi.ryusuke@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in nilfs_btree_assign
------------[ cut here ]------------
WARNING: CPU: 1 PID: 6898 at fs/nilfs2/btree.c:2301 nilfs_btree_assign+0xabb/0xd20 fs/nilfs2/btree.c:2301
Modules linked in:
CPU: 1 UID: 0 PID: 6898 Comm: segctord Not tainted 6.13.0-rc7-syzkaller-gc45323b7560e-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:nilfs_btree_assign+0xabb/0xd20 fs/nilfs2/btree.c:2301
Code: 00 00 44 89 f0 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 a2 53 24 fe 4c 8b 7c 24 38 eb a2 e8 96 53 24 fe 90 <0f> 0b 90 41 be fe ff ff ff eb 91 44 89 f1 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc90003137600 EFLAGS: 00010293
RAX: ffffffff837b1e8a RBX: ffff8880714f3fd8 RCX: ffff88802e24da00
RDX: 0000000000000000 RSI: 00000000fffffffe RDI: 00000000fffffffe
RBP: ffffc90003137730 R08: ffffffff837b17cb R09: 0000000000000000
R10: ffffc90003137560 R11: fffff52000626eaf R12: dffffc0000000000
R13: ffff88802a22ad00 R14: 00000000fffffffe R15: 1ffff92000626ed0
FS: 0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb73deff000 CR3: 000000000e736000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
nilfs_bmap_assign+0x8f/0x160 fs/nilfs2/bmap.c:390
nilfs_segctor_update_payload_blocknr fs/nilfs2/segment.c:1633 [inline]
nilfs_segctor_assign fs/nilfs2/segment.c:1667 [inline]
nilfs_segctor_do_construct+0x35c5/0x6ea0 fs/nilfs2/segment.c:2126
nilfs_segctor_construct+0x181/0x6b0 fs/nilfs2/segment.c:2479
nilfs_segctor_thread_construct fs/nilfs2/segment.c:2587 [inline]
nilfs_segctor_thread+0x69e/0xe80 fs/nilfs2/segment.c:2701
kthread+0x2f0/0x390 kernel/kthread.c:389
ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
</TASK>
Tested on:
commit: c45323b7 Merge tag 'mm-hotfixes-stable-2025-01-13-00-0..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17252a18580000
kernel config: https://syzkaller.appspot.com/x/.config?x=c676c8e1379fdfaa
dashboard link: https://syzkaller.appspot.com/bug?extid=158be45e4d99232e1900
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=160401f8580000
next prev parent reply other threads:[~2025-01-14 10:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 7:40 [syzbot] [nilfs?] WARNING in nilfs_btree_assign (3) syzbot
2025-01-14 10:34 ` Ryusuke Konishi
2025-01-14 10:51 ` syzbot [this message]
2025-01-14 11:28 ` Ryusuke Konishi
2025-01-14 12:28 ` 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=67864197.050a0220.216c54.0072.GAE@google.com \
--to=syzbot+158be45e4d99232e1900@syzkaller.appspotmail.com \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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.