From: syzbot <syzbot+12479ae15958fc3f54ec@syzkaller.appspotmail.com>
To: brauner@kernel.org, eadavis@qq.com, gnoack@google.com,
hdanton@sina.com, jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, max.kellermann@ionos.com,
mic@digikod.net, syzkaller-bugs@googlegroups.com,
twuufnxlz@gmail.com, viro@zeniv.linux.org.uk
Subject: Re: [syzbot] [fs?] BUG: sleeping function called from invalid context in hook_sb_delete
Date: Thu, 09 Oct 2025 13:56:03 -0700 [thread overview]
Message-ID: <68e82163.050a0220.3897dc.00a3.GAE@google.com> (raw)
In-Reply-To: <68d32659.a70a0220.4f78.0012.GAE@google.com>
syzbot has bisected this issue to:
commit 2ef435a872abc347dc0a92f1c213bb0af3cbf195
Author: Max Kellermann <max.kellermann@ionos.com>
Date: Wed Sep 17 15:36:31 2025 +0000
fs: add might_sleep() annotation to iput() and more
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1092ba7c580000
start commit: 7c3ba4249a36 Add linux-next specific files for 20251008
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1292ba7c580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1492ba7c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=fa7a95b14b1eaa
dashboard link: https://syzkaller.appspot.com/bug?extid=12479ae15958fc3f54ec
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12280dcd980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=111d852f980000
Reported-by: syzbot+12479ae15958fc3f54ec@syzkaller.appspotmail.com
Fixes: 2ef435a872ab ("fs: add might_sleep() annotation to iput() and more")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-10-09 20:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 22:59 [syzbot] [fs?] BUG: sleeping function called from invalid context in hook_sb_delete syzbot
2025-09-24 0:28 ` Hillf Danton
2025-09-24 0:56 ` syzbot
2025-09-24 9:44 ` Edward Adam Davis
2025-09-24 10:43 ` syzbot
2025-09-24 10:38 ` Edward Adam Davis
2025-09-24 10:46 ` Edward Adam Davis
2025-09-24 10:46 ` syzbot
2025-09-24 11:19 ` syzbot
2025-09-24 11:05 ` Jan Kara
2025-09-29 8:51 ` Christian Brauner
2025-10-09 20:56 ` syzbot [this message]
2025-11-01 15:32 ` Forwarded: " syzbot
2025-11-05 19:38 ` Forwarded: [PATCH v1] fs: Move might_sleep() annotation to iput_final() syzbot
[not found] <4f6e21b7-3c0d-4f99-bf3a-3f20fafa9591n@googlegroups.com>
2025-09-24 10:55 ` [syzbot] [fs?] BUG: sleeping function called from invalid context in hook_sb_delete syzbot
[not found] <20251101153157.837686-1-m@maowtm.org>
2025-11-01 16:18 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2025-11-05 19:37 [PATCH v1] fs: Move might_sleep() annotation to iput_final() Mickaël Salaün
2025-11-05 20:56 ` [syzbot] [fs?] BUG: sleeping function called from invalid context in hook_sb_delete syzbot
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=68e82163.050a0220.3897dc.00a3.GAE@google.com \
--to=syzbot+12479ae15958fc3f54ec@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--cc=eadavis@qq.com \
--cc=gnoack@google.com \
--cc=hdanton@sina.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=max.kellermann@ionos.com \
--cc=mic@digikod.net \
--cc=syzkaller-bugs@googlegroups.com \
--cc=twuufnxlz@gmail.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.