ufs: ufs_trunc_...() has exclusion with everything that might cause allocations
authorAl Viro <viro@zeniv.linux.org.uk>
Tue, 16 Jun 2015 22:45:21 +0000 (18:45 -0400)
committerAl Viro <viro@zeniv.linux.org.uk>
Mon, 6 Jul 2015 21:39:28 +0000 (17:39 -0400)
commit687857930d9294100a4636e45b78a244e6ba4125
treef7929d352818e1d8a8b4cd2b9bcac07dbc92df50
parent6a799d3514217d217b4e74a1ee4f016428582dc5
ufs: ufs_trunc_...() has exclusion with everything that might cause allocations

Currently - on lock_ufs(), eventually - on per-inode mutex.
lock_ufs() used to be mere BKL, which is much weaker, so it needed
those rechecks.  BKL doesn't provide any exclusion once we lose CPU;
its blind replacement, OTOH, _does_.  Making that per-filesystem was
an atrocity, but at least we can simplify life here.  And yes, we
certainly need to make that sucker per-inode - these days inode.c and
truncate.c uses are needed only to protect the block pointers.

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
fs/ufs/truncate.c