mail_bug.txt

{{if .First -}}
Hello,

{{end -}}
syzbot {{if .First}}found{{else}}has found a reproducer for{{end}} the following issue on:

HEAD commit:    {{formatTagHash .KernelCommit}} {{formatCommitTableTitle .KernelCommitTitle}}
git tree:       {{.KernelRepoAlias}}
{{if .LogLink}}console output: {{.LogLink}}
{{end}}{{if .KernelConfigLink}}kernel config:  {{.KernelConfigLink}}
{{end}}dashboard link: {{.Link}}
{{if .CompilerID}}compiler:       {{.CompilerID}}
{{end}}{{if .UserSpaceArch}}userspace arch: {{.UserSpaceArch}}
{{end}}{{if .ReproSyzLink}}syz repro:      {{.ReproSyzLink}}
{{end}}{{if .ReproCLink}}C reproducer:   {{.ReproCLink}}
{{end}}{{if and .Moderation .Maintainers}}CC:             {{.Maintainers}}
{{end}}{{if and (not .NoRepro) (not .ReproCLink) (not .ReproSyzLink)}}
Unfortunately, I don't have any reproducer for this issue yet.
{{end}}
{{if .BisectCause}}{{if .BisectCause.Commit}}The issue was bisected to:

commit {{.BisectCause.Commit.Hash}}
Author: {{.BisectCause.Commit.AuthorName}} <{{.BisectCause.Commit.Author}}>
Date:   {{formatKernelTime .BisectCause.Commit.Date}}

    {{.BisectCause.Commit.Title}}
{{else if .BisectCause.Commits}}Bisection is inconclusive: the first bad commit could be any of:
{{range $com := .BisectCause.Commits}}
{{formatTagHash $com.Hash}} {{$com.Title}}{{end}}
{{else}}Bisection is inconclusive: the issue happens on the oldest tested release.
{{end}}
bisection log:  {{.BisectCause.LogLink}}
{{if .BisectCause.CrashReportLink}}final oops:     {{.BisectCause.CrashReportLink}}
{{end}}{{if .BisectCause.CrashLogLink}}console output: {{.BisectCause.CrashLogLink}}
{{end}}
{{end}}IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: {{.CreditEmail}}
{{if .BisectCause}}{{if .BisectCause.Commit}}Fixes: {{formatTagHash .BisectCause.Commit.Hash}} ("{{.BisectCause.Commit.Title}}")
{{end}}{{end}}
{{printf "%s" .Report}}
{{if .First}}
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.{{if .BisectCause}}
For information about bisection process see: https://goo.gl/tpsmEJ#bisection{{end}}{{if or .ReproCLink .ReproSyzLink}}
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
{{- end -}}
{{- end -}}