All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+64d1c4bd2e3fa680321d@syzkaller.appspotmail.com>
To: jack@suse.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] [udf?] WARNING in __brelse (2)
Date: Wed, 01 Mar 2023 08:54:02 -0800	[thread overview]
Message-ID: <0000000000002bd5ae05f5d98f4f@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    2ebd1fbb946d Merge branch 'for-next/core' into for-kernelci
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=144829a8c80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=3519974f3f27816d
dashboard link: https://syzkaller.appspot.com/bug?extid=64d1c4bd2e3fa680321d
compiler:       Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/16985cc7a274/disk-2ebd1fbb.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fd3452567115/vmlinux-2ebd1fbb.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c75510922212/Image-2ebd1fbb.gz.xz

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

 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:591
------------[ cut here ]------------
VFS: brelse: Trying to free free buffer
WARNING: CPU: 1 PID: 13690 at fs/buffer.c:1145 __brelse+0x84/0xd8 fs/buffer.c:1145
Modules linked in:
CPU: 1 PID: 13690 Comm: syz-executor.1 Not tainted 6.2.0-syzkaller-18300-g2ebd1fbb946d #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __brelse+0x84/0xd8 fs/buffer.c:1145
lr : __brelse+0x84/0xd8 fs/buffer.c:1145
sp : ffff8000222f7600
x29: ffff8000222f7600 x28: ffff8000222f7760 x27: ffff000130521080
x26: ffff8000222f77b0 x25: 1ffff0000445ef00 x24: ffff0000dd9088d0
x23: ffff70000445eed8 x22: 1ffff0000445eee4 x21: ffff00013fc33d98
x20: 0000000000000000 x19: ffff00013fc33df8 x18: 1fffe0003689f976
x17: ffff800015b8d000 x16: ffff80001235d16c x15: 0000000000000000
x14: 1ffff00002b720af x13: dfff800000000000 x12: 0000000000040000
x11: 0000000000016792 x10: ffff80001ffaa000 x9 : 93de21cc8eb3a600
x8 : 93de21cc8eb3a600 x7 : ffff800008288c58 x6 : 0000000000000000
x5 : 0000000000000001 x4 : 0000000000000001 x3 : ffff80000aae9f90
x2 : ffff0001b44fcf08 x1 : 0000000100000000 x0 : 0000000000000027
Call trace:
 __brelse+0x84/0xd8 fs/buffer.c:1145
 brelse include/linux/buffer_head.h:326 [inline]
 udf_rename+0xd1c/0x10b0 fs/udf/namei.c:1214
 vfs_rename+0x9e0/0xe80 fs/namei.c:4779
 do_renameat2+0x95c/0x100c fs/namei.c:4930
 __do_sys_renameat2 fs/namei.c:4963 [inline]
 __se_sys_renameat2 fs/namei.c:4960 [inline]
 __arm64_sys_renameat2+0xe0/0xfc fs/namei.c:4960
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x64/0x198 arch/arm64/kernel/syscall.c:193
 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:591
irq event stamp: 7128
hardirqs last  enabled at (7127): [<ffff800008288cf8>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1370 [inline]
hardirqs last  enabled at (7127): [<ffff800008288cf8>] finish_lock_switch+0xbc/0x1e4 kernel/sched/core.c:5055
hardirqs last disabled at (7128): [<ffff800012358d60>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:405
softirqs last  enabled at (7094): [<ffff800008020ea8>] softirq_handle_end kernel/softirq.c:414 [inline]
softirqs last  enabled at (7094): [<ffff800008020ea8>] __do_softirq+0xd4c/0xfa4 kernel/softirq.c:600
softirqs last disabled at (7079): [<ffff80000802b4a4>] ____do_softirq+0x14/0x20 arch/arm64/kernel/irq.c:80
---[ end trace 0000000000000000 ]---


---
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-03-01 16: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=0000000000002bd5ae05f5d98f4f@google.com \
    --to=syzbot+64d1c4bd2e3fa680321d@syzkaller.appspotmail.com \
    --cc=jack@suse.com \
    --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.