On Tue, Jan 11, 2022 at 03:21:50PM +0800, cruise k wrote: > Hi, > > Syzkaller found the following issue: > > HEAD commit: 75acfdb Linux 5.16-rc8 > git tree: upstream > console output: https://pastebin.com/raw/YNZPt1rA > kernel config: https://pastebin.com/raw/XsnKfdRt > > And hope the report log can help you. Much more helpful than any of these things would be a description of what the test _does_. Seeing a stack trace after the problem has occurred isn't much help for tracking down what events caused the problem; to do that we need to know what was happening before the problem occurred. There are two relatively easy things you could do that might also help a little: Decode the addresses in the stack dump into source line numbers (probably requires that the kernel be built with debugging information). Make the console output document in pastebin.com include the _complete_ console output, not just the part starting from when the problem was detected. Alan Stern
