From: Thomas Gleixner Date: Wed, 20 Feb 2013 19:06:20 +0000 (-0500) Subject: btrfs: Init io_lock after cloning btrfs device struct X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=1cba0cdf5e4dbcd9e5fa5b54d7a028e55e2ca057;p=GitHub%2Fexynos8895%2Fandroid_kernel_samsung_universal8895.git btrfs: Init io_lock after cloning btrfs device struct __btrfs_close_devices() clones btrfs device structs with memcpy(). Some of the fields in the clone are reinitialized, but it's missing to init io_lock. In mainline this goes unnoticed, but on RT it leaves the plist pointing to the original about to be freed lock struct. Initialize io_lock after cloning, so no references to the original struct are left. Reported-and-tested-by: Mike Galbraith Cc: stable@vger.kernel.org Signed-off-by: Thomas Gleixner Signed-off-by: Chris Mason --- diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c index 7992dc4ea4cc..5d6010ba8b7e 100644 --- a/fs/btrfs/volumes.c +++ b/fs/btrfs/volumes.c @@ -650,6 +650,7 @@ static int __btrfs_close_devices(struct btrfs_fs_devices *fs_devices) new_device->writeable = 0; new_device->in_fs_metadata = 0; new_device->can_discard = 0; + spin_lock_init(&new_device->io_lock); list_replace_rcu(&device->dev_list, &new_device->dev_list); call_rcu(&device->rcu, free_device);