Mark Johnston cd32b4f5b7 Fix a deadlock in the FreeBSD getpages VOP ... FreeBSD has a per-page "busy" lock which is held when handling a page fault on a mapped file. This lock is also acquired when copying data from the DMU to the page cache in zfs_write(). File range locks are also acquired in both of these paths, in the opposite order with respect to the busy lock. In the getpages VOP, the range lock is only used to determine the extent of optional read-ahead and read-behind operations. To resolve the lock order reversal, modify the getpages VOP to avoid blocking on the range lock. Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov> Reviewed-by: Ryan Moeller <ryan@ixsystems.com> Signed-off-by: Mark Johnston <markj@FreeBSD.org> Closes #10519		2020-07-06 11:53:57 -07:00
..
freebsd	Fix a deadlock in the FreeBSD getpages VOP	2020-07-06 11:53:57 -07:00
linux	Clean up OS-specific ARC and kmem code	2020-06-29 09:01:07 -07:00