RE: [REPORT] libata deadlock possibilities by DEPT

[REPORT] libata deadlock possibilities by DEPT · Byungchul Park <hidden> · 2022-02-16
Report 2 in ata_scsi_port_error_handler() · Byungchul Park <hidden> · 2022-02-16
Report in ata_scsi_port_error_handler() · Byungchul Park <hidden> · 2022-02-16
Re: Report in ata_scsi_port_error_handler() · Damien Le Moal <hidden> · 2022-02-16
Re: Report in ata_scsi_port_error_handler() · Linus Torvalds <torvalds@linux-foundation.org> · 2022-02-16
Re: Report in ata_scsi_port_error_handler() · Steven Rostedt <rostedt@goodmis.org> · 2022-02-16
Re: Report in ata_scsi_port_error_handler() · Byungchul Park <hidden> · 2022-02-17
Re: Report in ata_scsi_port_error_handler() · Byungchul Park <hidden> · 2022-02-17
Report 3 in ata_scsi_port_error_handler() · Byungchul Park <hidden> · 2022-02-16
RE: [REPORT] libata deadlock possibilities by DEPT · Byungchul Park <hidden> · 2022-02-16

From: Byungchul Park <hidden>
Date: 2022-02-16 07:22:51
Also in: linux-fsdevel, linux-ide, linux-mm, lkml

Thanks to Matthew, I found the reports are spurious.. I missed the case
that it's not going to real sleep after preparing a wait.

I'm sorry for bothering you guys. Please ignore the reports.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help