From: syzbot <syzbot+12b178b7c756664d2518@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tbsthitw@gmail.com
Subject: Re: [syzbot] [fuse?] BUG: scheduling while atomic in __synchronize_srcu
Date: Sun, 12 Apr 2026 21:42:03 -0700 [thread overview]
Message-ID: <69dc741b.050a0220.3030df.0042.GAE@google.com> (raw)
In-Reply-To: <CAFmunOkwRk531XZV61BTX09hU75YGmzi8sXTvZKGSYDOB+QFMA@mail.gmail.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file Makefile
patch: **** unexpected end of file in patch
Tested on:
commit: 028ef9c9 Linux 7.0
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=2d08886358f27e8c
dashboard link: https://syzkaller.appspot.com/bug?extid=12b178b7c756664d2518
compiler:
userspace arch: arm64
patch: https://syzkaller.appspot.com/x/patch.diff?x=14f55b02580000
next parent reply other threads:[~2026-04-13 4:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFmunOkwRk531XZV61BTX09hU75YGmzi8sXTvZKGSYDOB+QFMA@mail.gmail.com>
2026-04-13 4:42 ` syzbot [this message]
[not found] <861pge2hdh.wl-maz@kernel.org>
2026-04-17 7:10 ` [syzbot] [fuse?] BUG: scheduling while atomic in __synchronize_srcu syzbot
[not found] <86340u3guc.wl-maz@kernel.org>
2026-04-16 18:24 ` syzbot
[not found] <864ila3h7q.wl-maz@kernel.org>
2026-04-16 18:16 ` syzbot
[not found] <20260413140408.072828@splitlinedeMacBook-Pro.local>
2026-04-13 8:37 ` syzbot
[not found] <20260413130810.085166@splitlinedeMacBook-Pro.local>
2026-04-13 8:09 ` syzbot
[not found] <20260413125214.050353@splitlinedeMacBook-Pro.local>
2026-04-13 5:03 ` syzbot
[not found] <20260413125018.045910@splitlinedeMacBook-Pro.local>
2026-04-13 5:03 ` syzbot
[not found] <20260413124911.042464@splitlinedeMacBook-Pro.local>
2026-04-13 5:02 ` syzbot
[not found] <20260411051419.20554-1-kartikey406@gmail.com>
2026-04-11 5:51 ` syzbot
2026-04-09 18:30 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=69dc741b.050a0220.3030df.0042.GAE@google.com \
--to=syzbot+12b178b7c756664d2518@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tbsthitw@gmail.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.