All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+742938912a8c5436cfed@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
	linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [btrfs?] WARNING in __btrfs_update_delayed_inode
Date: Sat, 25 Feb 2023 19:51:43 -0800	[thread overview]
Message-ID: <000000000000dace2005f592479a@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    9e58df973d22 Merge tag 'irq-core-2023-02-20' of git://git...
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11aa59f7480000
kernel config:  https://syzkaller.appspot.com/x/.config?x=2ac7065d93fcf412
dashboard link: https://syzkaller.appspot.com/bug?extid=742938912a8c5436cfed
compiler:       Debian clang version 15.0.7, 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/b4f13d97f464/disk-9e58df97.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1f533b623da7/vmlinux-9e58df97.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0288113d3224/bzImage-9e58df97.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+742938912a8c5436cfed@syzkaller.appspotmail.com

------------[ cut here ]------------
BTRFS: Transaction aborted (error -28)
WARNING: CPU: 1 PID: 6353 at fs/btrfs/delayed-inode.c:1065 __btrfs_update_delayed_inode+0x8f0/0xab0 fs/btrfs/delayed-inode.c:1065
Modules linked in:
CPU: 1 PID: 6353 Comm: btrfs-transacti Not tainted 6.2.0-syzkaller-02172-g9e58df973d22 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023
RIP: 0010:__btrfs_update_delayed_inode+0x8f0/0xab0 fs/btrfs/delayed-inode.c:1065
Code: 8c aa f8 ff ff be 08 00 00 00 4c 89 e7 e8 b8 2c 3d fe e9 98 f8 ff ff e8 2e e7 e7 fd 48 c7 c7 40 3a 2b 8b 89 de e8 f0 0f af fd <0f> 0b e9 3a ff ff ff 89 d1 80 e1 07 80 c1 03 38 c1 0f 8c 6a f9 ff
RSP: 0018:ffffc90016297700 EFLAGS: 00010246
RAX: 47bd4e3c7cf3e600 RBX: 00000000ffffffe4 RCX: ffff888024020000
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: ffffc90016297850 R08: ffffffff81532f72 R09: fffff52002c52e59
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: ffff88802b938001 R14: ffff888012b86cc8 R15: 1ffff11002570d99
FS:  0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f829a785058 CR3: 0000000042388000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 btrfs_update_delayed_inode fs/btrfs/delayed-inode.c:1099 [inline]
 __btrfs_commit_inode_delayed_items+0x234a/0x2400 fs/btrfs/delayed-inode.c:1119
 __btrfs_run_delayed_items+0x1db/0x430 fs/btrfs/delayed-inode.c:1153
 btrfs_commit_transaction+0xa34/0x3440 fs/btrfs/transaction.c:2264
 transaction_kthread+0x326/0x4c0 fs/btrfs/disk-io.c:1818
 kthread+0x270/0x300 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </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.

                 reply	other threads:[~2023-02-26  3:54 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=000000000000dace2005f592479a@google.com \
    --to=syzbot+742938912a8c5436cfed@syzkaller.appspotmail.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --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.