diff options
| author | Al Viro <viro@zeniv.linux.org.uk> | 2022-05-18 02:13:40 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2022-06-06 08:43:36 +0200 |
| commit | 20b413c38b7c36b4251f55ec656644d10af59e2f (patch) | |
| tree | 2f86bc18c3aa0e2e3d350028e74ea7c2dde2e507 /lib | |
| parent | 8243f5768dea24fe286a6323dc200225e7cff891 (diff) | |
| download | linux-stable-20b413c38b7c36b4251f55ec656644d10af59e2f.tar.gz linux-stable-20b413c38b7c36b4251f55ec656644d10af59e2f.tar.bz2 linux-stable-20b413c38b7c36b4251f55ec656644d10af59e2f.zip | |
percpu_ref_init(): clean ->percpu_count_ref on failure
[ Upstream commit a91714312eb16f9ecd1f7f8b3efe1380075f28d4 ]
That way percpu_ref_exit() is safe after failing percpu_ref_init().
At least one user (cgroup_create()) had a double-free that way;
there might be other similar bugs. Easier to fix in percpu_ref_init(),
rather than playing whack-a-mole in sloppy users...
Usual symptoms look like a messed refcounting in one of subsystems
that use percpu allocations (might be percpu-refcount, might be
something else). Having refcounts for two different objects share
memory is Not Nice(tm)...
Reported-by: syzbot+5b1e53987f858500ec00@syzkaller.appspotmail.com
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'lib')
| -rw-r--r-- | lib/percpu-refcount.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/lib/percpu-refcount.c b/lib/percpu-refcount.c index af9302141bcf..e5c5315da274 100644 --- a/lib/percpu-refcount.c +++ b/lib/percpu-refcount.c @@ -76,6 +76,7 @@ int percpu_ref_init(struct percpu_ref *ref, percpu_ref_func_t *release, data = kzalloc(sizeof(*ref->data), gfp); if (!data) { free_percpu((void __percpu *)ref->percpu_count_ptr); + ref->percpu_count_ptr = 0; return -ENOMEM; } |