Messages in this thread |  | | Date | Sat, 2 Apr 2022 20:26:23 +0900 | Subject | Re: [syzbot] INFO: task can't die in blkdev_common_ioctl | From | Tetsuo Handa <> |
| |
On 2022/04/02 16:20, syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit: f81e94e91878 Add linux-next specific files for 20211125 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=168d578db00000 > kernel config: https://syzkaller.appspot.com/x/.config?x=be9183de0824e4d7 > dashboard link: https://syzkaller.appspot.com/bug?extid=4f1a237abaf14719db49 > compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2 > > Unfortunately, I don't have any reproducer for this issue yet.
This is a known problem, and Christoph does not like a mitigation patch. https://lkml.kernel.org/r/YgoQBTzb3b0l1SzP@infradead.org
> > IMPORTANT: if you fix the issue, please add the following tag to the commit: > Reported-by: syzbot+4f1a237abaf14719db49@syzkaller.appspotmail.com
#syz dup: INFO: task hung in blkdev_fallocate
|  |