All of lore.kernel.org
 help / color / mirror / Atom feed
From: Justin Lai <justinlai0215@realtek.com>
To: Yunsheng Lin <linyunsheng@huawei.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: Report on abnormal behavior of "page_pool" API
Date: Thu, 1 Feb 2024 02:37:02 +0000	[thread overview]
Message-ID: <c686cf0065b74c139e34c4c7dd700301@realtek.com> (raw)
In-Reply-To: <e9beff86-ba0e-ad3c-1972-16cdc3b29ab3@huawei.com>

> On 2024/1/31 15:31, Justin Lai wrote:
> > To whom it may concern,
> >
> > I hope this email finds you well. I am writing to report a behavior
> > which seems to be abnormal.
> >
> > When I remove the module, I call page_pool_destroy() to release the
> 
> Which module?
The PCIe driver
> 
> > page_pool, but this message appears, page_pool_release_retry() stalled
> > pool shutdown 1024 inflight 120 sec. Then I tried to return the page
> > to page_pool before calling page_pool_destroy(), so I called
> > page_pool_put_full_page() first, but after doing so, this message was
> > printed, page_pool_empty_ring() page_pool refcnt 0 violation, and the
> 
> As we have "page_ref_count(page) == 1" checking to allow recycling page in
> pool->ring:
> https://elixir.bootlin.com/linux/v6.8-rc2/source/net/core/page_pool.c#L654
> 
> It seems somebody is still using the page and manipulating _refcount while the
> page is sitting in the pool->ring?

I will confirm this part again, thank you for your reply.
> 
> 
> > computer crashed.
> >
> > I would like to ask what could be causing this and how I should fix it.
> 
> Not sure if you read the below doc for page_pool, understanding the internal
> detail and the API usages may help you debuging the problem:
> Documentation/networking/page_pool.rst

Thank you for your reply. I have read this document, but I will study it again.
> 
> >
> > The information on my working environment is: Ubuntu23.10, linux
> > kernel 6.4, 6.5, 6.6
> >
> > Thank you for your time and efforts, I am looking forward to your reply.
> >
> > Best regards,
> > Justin
> >
> > .
> >

  reply	other threads:[~2024-02-01  2:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31  7:31 Report on abnormal behavior of "page_pool" API Justin Lai
2024-01-31  8:56 ` Yunsheng Lin
2024-02-01  2:37   ` Justin Lai [this message]
2024-01-31 19:15 ` Gerhard Engleder
2024-02-01  2:42   ` Justin Lai

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=c686cf0065b74c139e34c4c7dd700301@realtek.com \
    --to=justinlai0215@realtek.com \
    --cc=linyunsheng@huawei.com \
    --cc=netdev@vger.kernel.org \
    /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.