Brian Behlendorf 57f5a2008e Fix txg_quiesce thread deadlock ... A deadlock was accidentally introduced by commit e95853a which can occur when the system is under memory pressure. What happens is that while the txg_quiesce thread is holding the tx->tx_cpu locks it enters memory reclaim. In the context of this memory reclaim it then issues synchronous I/O to a ZVOL swap device. Because the txg_quiesce thread is holding the tx->tx_cpu locks a new txg cannot be opened to handle the I/O. Deadlock. The fix is straight forward. Move the memory allocation outside the critical region where the tx->tx_cpu locks are held. And for good measure change the offending allocation to KM_PUSHPAGE to ensure it never attempts to issue I/O during reclaim. Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Issue #1274		2013-04-26 14:42:36 -07:00
..
avl	Add script for builtin module building.	2012-07-26 13:45:09 -07:00
nvpair	Illumos #2619 and #2747	2013-01-08 10:35:35 -08:00
unicode	Add script for builtin module building.	2012-07-26 13:45:09 -07:00
zcommon	Add snapdev=[hidden|visible] dataset property	2013-03-05 12:37:54 -08:00
zfs	Fix txg_quiesce thread deadlock	2013-04-26 14:42:36 -07:00
zpios	Refresh links to web site	2013-03-06 15:46:41 -08:00
.gitignore	gitignore: anchor entries at their respective directory	2013-04-02 10:50:17 -07:00
Makefile.in	Add KMODDIR to install target	2013-03-06 15:46:40 -08:00