lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20180111201011.GG19241@thunk.org> Date: Thu, 11 Jan 2018 15:10:11 -0500 From: Theodore Ts'o <tytso@....edu> To: Riccardo Schirone <sirmy15@...il.com> Cc: adilger.kernel@...ger.ca, linux-ext4@...r.kernel.org Subject: Re: [PATCH 1/3] fs/ext4: release kobject/kset even when init/register fail On Tue, Nov 28, 2017 at 12:17:59AM +0100, Riccardo Schirone wrote: > Even when kobject_init_and_add/kset_register fail, the kobject has been > already initialized and the refcount set to 1. Thus it is necessary to > release the kobject/kset, to avoid the memory associated with it hanging > around forever. > > Signed-off-by: Riccardo Schirone <sirmy15@...il.com> Thanks, applied. - Ted
Powered by blists - more mailing lists