From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: syzbot <syzbot+27f8c9169772defbdde9@syzkaller.appspotmail.com>,
syzkaller-bugs@googlegroups.com,
Johannes Weiner <hannes@cmpxchg.org>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org
Subject: Re: [syzbot] [mm?] possible deadlock in free_pcppages_bulk
Date: Fri, 22 Sep 2023 19:27:15 +0900 [thread overview]
Message-ID: <a4b5cfc6-cd8e-a3e6-cabb-3a29881e6967@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <000000000000099f0d0605e18c69@google.com>
It is not safe to call printk() with zone->lock held.
Closing this report because "mm: page_alloc: consolidate free page accounting"
was removed from linux-next tree.
#syz invalid
On 2023/09/22 2:08, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: dfa449a58323 Add linux-next specific files for 20230915
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=110f76f8680000
> kernel config: https://syzkaller.appspot.com/x/.config?x=e204dda2e58397ec
> dashboard link: https://syzkaller.appspot.com/bug?extid=27f8c9169772defbdde9
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/34f9995871ed/disk-dfa449a5.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/95e2e1c3ab9e/vmlinux-dfa449a5.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/cfc6db9684d4/bzImage-dfa449a5.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+27f8c9169772defbdde9@syzkaller.appspotmail.com
prev parent reply other threads:[~2023-09-22 10:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 17:08 syzbot
2023-09-22 10:27 ` Tetsuo Handa [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=a4b5cfc6-cd8e-a3e6-cabb-3a29881e6967@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+27f8c9169772defbdde9@syzkaller.appspotmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox