All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+d285c6d0b23c6033d520@syzkaller.appspotmail.com>
To: aivazian.tigran@gmail.com, brauner@kernel.org,
	jfs-discussion@lists.sourceforge.net,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	shaggy@kernel.org, syzkaller-bugs@googlegroups.com,
	viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [jfs?] KASAN: null-ptr-deref Read in drop_buffers (2)
Date: Mon, 11 Sep 2023 21:06:55 -0700	[thread overview]
Message-ID: <000000000000ce87a006052192ea@google.com> (raw)
In-Reply-To: <00000000000054e4d10601e44b24@google.com>

syzbot has found a reproducer for the following issue on:

HEAD commit:    0bb80ecc33a8 Linux 6.6-rc1
git tree:       upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=123943c8680000
kernel config:  https://syzkaller.appspot.com/x/.config?x=df91a3034fe3f122
dashboard link: https://syzkaller.appspot.com/bug?extid=d285c6d0b23c6033d520
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=13802378680000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=13e15844680000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/dd8655c7bc5f/disk-0bb80ecc.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4e170fb1db75/vmlinux-0bb80ecc.xz
kernel image: https://storage.googleapis.com/syzbot-assets/88d7ab5b54cd/bzImage-0bb80ecc.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/0fc14e142a3d/mount_0.gz

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

find_entry called with index = 0
read_mapping_page failed!
ERROR: (device loop0): txCommit: 
ERROR: (device loop0): remounting filesystem as read-only
==================================================================
BUG: KASAN: null-ptr-deref in instrument_atomic_read include/linux/instrumented.h:68 [inline]
BUG: KASAN: null-ptr-deref in atomic_read include/linux/atomic/atomic-instrumented.h:32 [inline]
BUG: KASAN: null-ptr-deref in buffer_busy fs/buffer.c:2896 [inline]
BUG: KASAN: null-ptr-deref in drop_buffers+0x6f/0x700 fs/buffer.c:2908
Read of size 4 at addr 0000000000000060 by task syz-executor224/5036

CPU: 1 PID: 5036 Comm: syz-executor224 Not tainted 6.6.0-rc1-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
 print_report+0xe6/0x540 mm/kasan/report.c:478
 kasan_report+0x175/0x1b0 mm/kasan/report.c:588
 kasan_check_range+0x27e/0x290 mm/kasan/generic.c:187
 instrument_atomic_read include/linux/instrumented.h:68 [inline]
 atomic_read include/linux/atomic/atomic-instrumented.h:32 [inline]
 buffer_busy fs/buffer.c:2896 [inline]
 drop_buffers+0x6f/0x700 fs/buffer.c:2908
 try_to_free_buffers+0x295/0x5f0 fs/buffer.c:2938
 shrink_folio_list+0x271a/0x8870 mm/vmscan.c:2068
 shrink_inactive_list mm/vmscan.c:2614 [inline]
 shrink_list mm/vmscan.c:2855 [inline]
 shrink_lruvec+0x16e6/0x2d30 mm/vmscan.c:6319
 shrink_node_memcgs mm/vmscan.c:6505 [inline]
 shrink_node+0x1176/0x28c0 mm/vmscan.c:6540
 shrink_zones mm/vmscan.c:6779 [inline]
 do_try_to_free_pages+0x717/0x19e0 mm/vmscan.c:6841
 try_to_free_mem_cgroup_pages+0x455/0xa50 mm/vmscan.c:7156
 try_charge_memcg+0x5e1/0x16e0 mm/memcontrol.c:2691
 obj_cgroup_charge_pages mm/memcontrol.c:3105 [inline]
 __memcg_kmem_charge_page+0x21e/0x380 mm/memcontrol.c:3131
 __alloc_pages+0x28b/0x670 mm/page_alloc.c:4443
 __alloc_pages_node include/linux/gfp.h:237 [inline]
 alloc_pages_node include/linux/gfp.h:260 [inline]
 bpf_ringbuf_area_alloc kernel/bpf/ringbuf.c:122 [inline]
 bpf_ringbuf_alloc+0xcb/0x420 kernel/bpf/ringbuf.c:170
 ringbuf_map_alloc+0x1d3/0x2f0 kernel/bpf/ringbuf.c:204
 map_create+0x849/0x1040 kernel/bpf/syscall.c:1207
 __sys_bpf+0x6a2/0x810 kernel/bpf/syscall.c:5317
 __do_sys_bpf kernel/bpf/syscall.c:5439 [inline]
 __se_sys_bpf kernel/bpf/syscall.c:5437 [inline]
 __x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:5437
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7ff75fb611c9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 11 1a 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:00007ffc0dbb0f28 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007ff75fb611c9
RDX: 0000000000000048 RSI: 0000000020000cc0 RDI: 0000000000000000
RBP: 00007ffc0dbb0f4c R08: ffffffffffffffff R09: ffffffffffffffff
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffc0dbb0fa0
R13: 00007ffc0dbb0f60 R14: 000000000000cf31 R15: 0000000000000001
 </TASK>
==================================================================


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

      reply	other threads:[~2023-09-12  4:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 22:44 [syzbot] [bfs?] KASAN: null-ptr-deref Read in drop_buffers (2) syzbot
2023-09-12  4:06 ` syzbot [this message]

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=000000000000ce87a006052192ea@google.com \
    --to=syzbot+d285c6d0b23c6033d520@syzkaller.appspotmail.com \
    --cc=aivazian.tigran@gmail.com \
    --cc=brauner@kernel.org \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaggy@kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=viro@zeniv.linux.org.uk \
    /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.