From: syzbot <syzbot+3b6c5c6a1d0119b687a1@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [afs?] BUG: sleeping function called from invalid context in __alloc_frozen_pages_noprof
Date: Fri, 28 Mar 2025 23:07:04 -0700 [thread overview]
Message-ID: <67e78e08.050a0220.1547ec.001e.GAE@google.com> (raw)
In-Reply-To: <tencent_43A5890D8A92615DC95DBA99714FD50D8207@qq.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file fs/afs/dynroot.c
Hunk #1 FAILED at 287.
Hunk #2 succeeded at 305 (offset -1 lines).
Hunk #3 succeeded at 356 (offset -1 lines).
1 out of 3 hunks FAILED
Tested on:
commit: 1d0b929f afs: Change dynroot to create contents on dem..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel config: https://syzkaller.appspot.com/x/.config?x=5f1762820c18874b
dashboard link: https://syzkaller.appspot.com/bug?extid=3b6c5c6a1d0119b687a1
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=17917804580000
next prev parent reply other threads:[~2025-03-29 6:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 16:26 [syzbot] [afs?] BUG: sleeping function called from invalid context in __alloc_frozen_pages_noprof syzbot
2025-03-28 17:44 ` David Howells
2025-03-28 18:15 ` syzbot
2025-03-29 2:47 ` Edward Adam Davis
2025-03-29 5:51 ` syzbot
2025-03-29 5:55 ` Edward Adam Davis
2025-03-29 6:07 ` syzbot [this message]
2025-03-29 9:39 ` Edward Adam Davis
2025-03-29 10:03 ` syzbot
2025-03-29 9:49 ` David Howells
2025-03-29 10:18 ` syzbot
2025-03-31 10:58 ` David Howells
2025-03-31 12:49 ` Aleksandr Nogikh
-- strict thread matches above, loose matches on Subject: below --
2025-03-27 16:27 [syzbot] [afs?] [ntfs3?] BUG: sleeping function called from invalid context in ovl_cache_entry_new syzbot
2025-03-29 2:53 ` [syzbot] [afs?] BUG: sleeping function called from invalid context in __alloc_frozen_pages_noprof Edward Adam Davis
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=67e78e08.050a0220.1547ec.001e.GAE@google.com \
--to=syzbot+3b6c5c6a1d0119b687a1@syzkaller.appspotmail.com \
--cc=eadavis@qq.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox