linux-kernel - Re: [PATCH] trace/blktrace: fix memory leak with using debugfs

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-prev] [day] [month] [year] [list]

Message-Id: <167570098443.24242.14188383758966607556.b4-ty@kernel.dk>
Date:   Mon, 06 Feb 2023 09:29:44 -0700
From:   Jens Axboe <axboe@...nel.dk>
To:     linux-trace-kernel@...r.kernel.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Steven Rostedt <rostedt@...dmis.org>,
        Masami Hiramatsu <mhiramat@...nel.org>,
        linux-block@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] trace/blktrace: fix memory leak with using
 debugfs_lookup()


On Thu, 02 Feb 2023 15:19:56 +0100, Greg Kroah-Hartman wrote:
> When calling debugfs_lookup() the result must have dput() called on it,
> otherwise the memory will leak over time.  To make things simpler, just
> call debugfs_lookup_and_remove() instead which handles all of the logic
> at once.
> 
> 

Applied, thanks!

[1/1] trace/blktrace: fix memory leak with using debugfs_lookup()
      commit: 83e8864fee26f63a7435e941b7c36a20fd6fe93e

Best regards,
-- 
Jens Axboe