Received-SPF: pass (google.com: domain of linux-kernel+bounces-195536-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
From: Jens Axboe <axboe@kernel.dk>
To: Pavel Begunkov <asml.silence@gmail.com>, 
 Breno Leitao <leitao@debian.org>
Cc: leit@meta.com, io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
In-Reply-To: <20240530142340.1248216-1-leitao@debian.org>
References: <20240530142340.1248216-1-leitao@debian.org>
Subject: Re: [PATCH] io_uring/rw: Free iovec before cleaning async data
Message-Id: <171707991426.532351.6222913434182120695.b4-ty@kernel.dk>
Date: Thu, 30 May 2024 08:38:34 -0600
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit


On Thu, 30 May 2024 07:23:39 -0700, Breno Leitao wrote:
> kmemleak shows that there is a memory leak in io_uring read operation,
> where a buffer is allocated at iovec import, but never de-allocated.
> 
> The memory is allocated at io_async_rw->free_iovec, but, then
> io_async_rw is kfreed, taking the allocated memory with it. I saw this
> happening when the read operation fails with -11 (EAGAIN).
> 
> [...]

Applied, thanks!

[1/1] io_uring/rw: Free iovec before cleaning async data
      commit: e112311615a24e1618a591c73506571dc304eb8d

Best regards,
-- 
Jens Axboe