Chris Mason e5e9a5206a Btrfs: avoid races between super writeout and device list updates
On multi-device filesystems, btrfs writes supers to all of the devices
before considering a sync complete.  There wasn't any additional
locking between super writeout and the device list management code
because device management was done inside a transaction and
super writeout only happened  with no transation writers running.

With the btrfs fsync log and other async transaction updates, this
has been racey for some time.  This adds a mutex to protect
the device list.  The existing volume mutex could not be reused due to
transaction lock ordering requirements.

Signed-off-by: Chris Mason <chris.mason@oracle.com>
2009-06-10 15:17:02 -04:00
..
2009-06-10 11:36:43 -04:00
2009-06-10 11:29:47 -04:00
2009-06-10 11:36:43 -04:00
2008-09-25 11:04:06 -04:00
2009-04-24 15:46:04 -04:00
2009-02-04 09:28:28 -05:00
2009-04-02 16:46:06 -04:00
2009-06-10 11:29:52 -04:00
2009-01-05 21:25:51 -05:00
2009-02-04 09:29:13 -05:00
2009-02-04 09:29:13 -05:00
2009-01-05 21:25:51 -05:00