From: syzbot <syzbot+f3c6fda1297c748a7076@syzkaller.appspotmail.com>
To: da.gomez@samsung.com, dave@stgolabs.net,
linux-kernel@vger.kernel.org, mcgrof@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] [fs?] BUG: sleeping function called from invalid context in folio_mc_copy
Date: Sat, 29 Mar 2025 21:21:03 -0700 [thread overview]
Message-ID: <67e8c6af.050a0220.1547ec.0089.GAE@google.com> (raw)
In-Reply-To: <Z-jCVfGaNHmLVN2i@bombadil.infradead.org>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
unregister_netdevice: waiting for DEV to become free
unregister_netdevice: waiting for batadv0 to become free. Usage count = 3
Tested on:
commit: 462c2cb1 mm/migrate: avoid atomic context on buffer_mi..
git tree: https://github.com/linux-kdevops/linux.git 20250529-ext4-migration-fix
console output: https://syzkaller.appspot.com/x/log.txt?x=141e0404580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1b79fdf1dd3782cc
dashboard link: https://syzkaller.appspot.com/bug?extid=f3c6fda1297c748a7076
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
next parent reply other threads:[~2025-03-30 4:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Z-jCVfGaNHmLVN2i@bombadil.infradead.org>
2025-03-30 4:21 ` syzbot [this message]
2025-03-30 4:59 ` [syzbot] [mm?] [fs?] BUG: sleeping function called from invalid context in folio_mc_copy Luis Chamberlain
2025-03-27 16:26 syzbot
2025-03-27 21:42 ` Luis Chamberlain
2025-03-30 2:05 ` Rik van Riel
2025-03-30 2:26 ` Luis Chamberlain
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=67e8c6af.050a0220.1547ec.0089.GAE@google.com \
--to=syzbot+f3c6fda1297c748a7076@syzkaller.appspotmail.com \
--cc=da.gomez@samsung.com \
--cc=dave@stgolabs.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@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.