All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+5ecbe63baca437585bd4@syzkaller.appspotmail.com>
To: len.brown@intel.com, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org, pavel@ucw.cz, rjw@rjwysocki.net,
	syzkaller-bugs@googlegroups.com
Subject: kernel BUG in memory_bm_free
Date: Tue, 02 Feb 2021 21:59:17 -0800	[thread overview]
Message-ID: <0000000000009c21de05ba6849e7@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    3aaf0a27 Merge tag 'clang-format-for-linux-v5.11-rc7' of g..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17ef6108d00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=10152c2ea16351e7
dashboard link: https://syzkaller.appspot.com/bug?extid=5ecbe63baca437585bd4
userspace arch: arm64

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

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

------------[ cut here ]------------
kernel BUG at kernel/power/snapshot.c:257!
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 2394 Comm: syz-executor.0 Not tainted 5.11.0-rc6-syzkaller-00055-g3aaf0a27ffc2 #0
Hardware name: linux,dummy-virt (DT)
pstate: 20400009 (nzCv daif +PAN -UAO -TCO BTYPE=--)
pc : free_image_page kernel/power/snapshot.c:257 [inline]
pc : free_image_page kernel/power/snapshot.c:253 [inline]
pc : free_list_of_pages kernel/power/snapshot.c:274 [inline]
pc : memory_bm_free+0x260/0x320 kernel/power/snapshot.c:726
lr : free_basic_memory_bitmaps+0x3c/0x90 kernel/power/snapshot.c:1173
sp : ffff8000163dbc50
x29: ffff8000163dbc50 x28: f4ff000025204070 
x27: ffff800012d4c000 x26: f4ff000025204008 
x25: f5ff00002827c700 x24: ffff800012d4c000 
x23: 00007fffffffffff x22: f4ff000025204018 
x21: 0000000000000001 x20: ffff800013b576d0 
x19: f5ff00002827c700 x18: 0000000000000000 
x17: 0000000000000000 x16: 0000000000000000 
x15: 0000000000000000 x14: 0000000000000000 
x13: 0000000000000000 x12: 0000000000000000 
x11: 0000000000000000 x10: 0000000000000000 
x9 : fcff000025205400 x8 : 0000000000000002 
x7 : f6ff000025205000 x6 : 00000000000001ff 
x5 : 0000000000000000 x4 : 0000000000000000 
x3 : ffff800013b576d0 x2 : f4ff00002517e000 
x1 : 0000000000000001 x0 : 0b0000002517e000 
Call trace:
 free_image_page kernel/power/snapshot.c:257 [inline]
 free_list_of_pages kernel/power/snapshot.c:274 [inline]
 memory_bm_free+0x260/0x320 kernel/power/snapshot.c:726
 free_basic_memory_bitmaps+0x3c/0x90 kernel/power/snapshot.c:1173
 snapshot_release+0x74/0x90 kernel/power/user.c:120
 __fput+0x78/0x230 fs/file_table.c:280
 ____fput+0x10/0x20 fs/file_table.c:313
 task_work_run+0x80/0x160 kernel/task_work.c:140
 tracehook_notify_resume include/linux/tracehook.h:189 [inline]
 do_notify_resume+0x20c/0x13e0 arch/arm64/kernel/signal.c:939
 work_pending+0xc/0x3d4
Code: cb000260 d34cfc00 97fcf6fe 35fffc20 (d4210000) 
---[ end trace 174c294156b0dfb3 ]---


---
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:[~2021-02-03  6:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03  5:59 syzbot [this message]
2021-02-03 13:38 ` syzbot spam -- is it useful? time to ban them from the list? [was Re: kernel BUG in memory_bm_free] Pavel Machek
2021-03-15  7:08 ` kernel BUG in memory_bm_free Dmitry Vyukov
2021-03-15 12:09   ` Catalin Marinas
2021-03-15 12:26     ` Dmitry Vyukov

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=0000000000009c21de05ba6849e7@google.com \
    --to=syzbot+5ecbe63baca437585bd4@syzkaller.appspotmail.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@rjwysocki.net \
    --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.