Andreas Gruenbacher b924bdab74 gfs2: Move the inode glock locking to gfs2_file_buffered_write
So far, for buffered writes, we were taking the inode glock in
gfs2_iomap_begin and dropping it in gfs2_iomap_end with the intention of
not holding the inode glock while iomap_write_actor faults in user
pages.  It turns out that iomap_write_actor is called inside iomap_begin
... iomap_end, so the user pages were still faulted in while holding the
inode glock and the locking code in iomap_begin / iomap_end was
completely pointless.

Move the locking into gfs2_file_buffered_write instead.  We'll take care
of the potential deadlocks due to faulting in user pages while holding a
glock in a subsequent patch.

Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
2021-10-20 19:33:09 +02:00
..
2019-07-03 14:45:18 +02:00
2021-06-29 10:56:51 +02:00
2021-06-29 10:56:51 +02:00
2021-04-29 10:33:35 -07:00
2021-08-19 12:31:17 -05:00
2021-06-29 10:56:51 +02:00
2021-02-17 19:30:28 +01:00
2021-04-08 15:07:21 +02:00