From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Kirti Wankhede <kwankhede@nvidia.com>,
Yan Zhao <yan.y.zhao@intel.com>,
Nikolay Kuratov <kniv@yandex-team.ru>,
Jiacheng Shi <billsjc@sjtu.edu.cn>,
Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [PATCH 5.10 5.15] vfio/iommu_type1: replace kfree with kvfree
Date: Sun, 21 Jun 2026 09:47:43 -0400 [thread overview]
Message-ID: <20260621133722.0005.sashal@kernel.org> (raw)
In-Reply-To: <20260619150206.1719815-1-kniv@yandex-team.ru>
> commit 2bed2ced40c97b8540ff38df0149e8ecb2bf4c65 upstream.
>
> Variables allocated by kvzalloc should not be freed by kfree.
> Because they may be allocated by vmalloc.
> So we replace kfree with kvfree here.
Queued for 5.10 and 5.15, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-06-21 13:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 15:02 [PATCH 5.10 5.15] vfio/iommu_type1: replace kfree with kvfree Nikolay Kuratov
2026-06-19 15:13 ` sashiko-bot
2026-06-21 13:47 ` Sasha Levin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260621133722.0005.sashal@kernel.org \
--to=sashal@kernel.org \
--cc=alex.williamson@redhat.com \
--cc=billsjc@sjtu.edu.cn \
--cc=kniv@yandex-team.ru \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=yan.y.zhao@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox