diff options
| author | Oleg Nesterov | 2015-08-21 19:42:55 +0200 |
|---|---|---|
| committer | Paul E. McKenney | 2015-10-06 11:25:26 -0700 |
| commit | 95b19f684c61ffc9b039e02c5d1113c2d8cd7105 (patch) | |
| tree | 5faf2eee589b2acb438a0881c2c3d80877f96bd5 /security | |
| parent | 07899a6e5f56136028c44a57ad0451e797365ac3 (diff) | |
locking/percpu-rwsem: Make percpu_free_rwsem() after kzalloc() safe
This is the temporary ugly hack which will be reverted later. We only
need it to ensure that the next patch will not break "change sb_writers
to use percpu_rw_semaphore" patches routed via the VFS tree.
The alloc_super()->destroy_super() error path assumes that it is safe
to call percpu_free_rwsem() after kzalloc() without percpu_init_rwsem(),
so let's not disappoint it.
Signed-off-by: Oleg Nesterov <oleg@redhat.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Reviewed-by: Josh Triplett <josh@joshtriplett.org>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions