From: Jakub Kicinski <kuba@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: "Toke Høiland-Jørgensen" <toke@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
"Jesper Dangaard Brouer" <hawk@kernel.org>,
"Saeed Mahameed" <saeedm@nvidia.com>,
"Leon Romanovsky" <leon@kernel.org>,
"Tariq Toukan" <tariqt@nvidia.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
"Simon Horman" <horms@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Mina Almasry" <almasrymina@google.com>,
"Yonglong Liu" <liuyonglong@huawei.com>,
"Yunsheng Lin" <linyunsheng@huawei.com>,
"Pavel Begunkov" <asml.silence@gmail.com>,
"Matthew Wilcox" <willy@infradead.org>,
netdev@vger.kernel.org, bpf@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-mm@kvack.org,
"Qiuling Ren" <qren@redhat.com>, "Yuying Ma" <yuma@redhat.com>,
gregkh@linuxfoundation.org, sashal@kernel.org
Subject: Re: [PATCH net-next v9 2/2] page_pool: Track DMA-mapped pages and unmap them when destroying the pool
Date: Wed, 11 Jun 2025 13:12:41 -0700 [thread overview]
Message-ID: <20250611131241.6ff7cf5d@kernel.org> (raw)
In-Reply-To: <aEmwYU/V/9/Ul04P@gmail.com>
On Wed, 11 Jun 2025 09:35:45 -0700 Breno Leitao wrote:
> On Wed, Apr 09, 2025 at 12:41:37PM +0200, Toke Høiland-Jørgensen wrote:
> > Fixes: ff7d6b27f894 ("page_pool: refurbish version of page_pool code")
>
> Do you have plan to backport this fix to LTS kernels? I am getting some
> of these crashes on older kernel, and I am curious if there are plans to
> backport this to LTS kernels.
I think it's worth disclosing that the crashes we see are in error
recovery on unstable HW. My vote would be to keep this out of stable
until it reaches at least one final release.
next prev parent reply other threads:[~2025-06-11 20:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 10:41 [PATCH net-next v9 0/2] Fix late DMA unmap crash for page pool Toke Høiland-Jørgensen
2025-04-09 10:41 ` [PATCH net-next v9 1/2] page_pool: Move pp_magic check into helper functions Toke Høiland-Jørgensen
2025-04-10 1:15 ` Zi Yan
2025-04-10 10:21 ` Toke Høiland-Jørgensen
2025-04-09 10:41 ` [PATCH net-next v9 2/2] page_pool: Track DMA-mapped pages and unmap them when destroying the pool Toke Høiland-Jørgensen
2025-06-11 16:35 ` Breno Leitao
2025-06-11 20:12 ` Jakub Kicinski [this message]
2025-06-12 7:25 ` Toke Høiland-Jørgensen
2025-06-12 14:05 ` Jakub Kicinski
2025-06-13 8:41 ` Toke Høiland-Jørgensen
2025-06-13 15:02 ` Jakub Kicinski
2025-06-20 11:01 ` Pedro Falcato
2025-04-15 0:30 ` [PATCH net-next v9 0/2] Fix late DMA unmap crash for page pool patchwork-bot+netdevbpf
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=20250611131241.6ff7cf5d@kernel.org \
--to=kuba@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=asml.silence@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=leitao@debian.org \
--cc=leon@kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linyunsheng@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qren@redhat.com \
--cc=saeedm@nvidia.com \
--cc=sashal@kernel.org \
--cc=tariqt@nvidia.com \
--cc=toke@redhat.com \
--cc=willy@infradead.org \
--cc=yuma@redhat.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;
as well as URLs for NNTP newsgroup(s).