From: Alex Elder <elder@linaro.org>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Cc: mka@chromium.org, evgreen@chromium.org,
bjorn.andersson@linaro.org, quic_cpratapa@quicinc.com,
quic_avuyyuru@quicinc.com, quic_jponduru@quicinc.com,
quic_subashab@quicinc.com, elder@kernel.org,
netdev@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/2] net: ipa: fix page free in two spots
Date: Sun, 22 May 2022 07:46:07 -0500 [thread overview]
Message-ID: <59c6347c-2689-24bf-47b8-b635fef2e530@linaro.org> (raw)
In-Reply-To: <20220522005959.1175181-1-elder@linaro.org>
On 5/21/22 7:59 PM, Alex Elder wrote:
> When a receive buffer is not wrapped in an SKB and passed to the
> network stack, the (compound) page gets freed within the IPA driver.
> This is currently quite rare.
>
> The pages are freed using __free_pages(), but they should instead be
> freed using page_put(). This series fixes this, in two spots.
>
> These patches work for Linux v5.18-rc7 and v5.17.y, but won't apply
> cleanly to earlier stable branches. (Nevertheless, the fix is
> trivial.)
>
> -Alex
I accidentally based this on net-next/master rather than net/master.
Sorry about that. I'll send version 2 in a few days.
-Alex
> Alex Elder (2):
> net: ipa: fix page free in ipa_endpoint_trans_release()
> net: ipa: fix page free in ipa_endpoint_replenish_one()
>
> drivers/net/ipa/ipa_endpoint.c | 9 +++------
> 1 file changed, 3 insertions(+), 6 deletions(-)
>
next prev parent reply other threads:[~2022-05-22 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 0:59 [PATCH net 0/2] net: ipa: fix page free in two spots Alex Elder
2022-05-22 0:59 ` [PATCH net 1/2] net: ipa: fix page free in ipa_endpoint_trans_release() Alex Elder
2022-05-22 0:59 ` [PATCH net 2/2] net: ipa: fix page free in ipa_endpoint_replenish_one() Alex Elder
2022-05-22 12:46 ` Alex Elder [this message]
2022-05-22 20:00 ` [PATCH net 0/2] net: ipa: fix page free in two spots David Miller
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=59c6347c-2689-24bf-47b8-b635fef2e530@linaro.org \
--to=elder@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=elder@kernel.org \
--cc=evgreen@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_avuyyuru@quicinc.com \
--cc=quic_cpratapa@quicinc.com \
--cc=quic_jponduru@quicinc.com \
--cc=quic_subashab@quicinc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.