linux-kernel - Re: [PATCH v2] afs: Fix memory leak in afs_put

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 1 Jun 2020 16:40:40 +0200
From:   Markus Elfring <Markus.Elfring@....de>
To:     Zhihao Cheng <chengzhihao1@...wei.com>,
        linux-afs@...ts.infradead.org, linux-fsdevel@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org, David Howells <dhowells@...hat.com>,
        Yi Zhang <yi.zhang@...wei.com>
Subject: Re: [PATCH v2] afs: Fix memory leak in afs_put_sysnames()

> sysnames should be freed after refcnt being decreased to zero in
> afs_put_sysnames().

How do you think about a wording variant like the following?

   Release the sysnames object after its reference counter was decreased
   to zero.

Will it matter to mention the size of the data structure "afs_sysnames"?

Regards,
Markus