From: Jonathan Lemon <jonathan.lemon@gmail.com>
To: <netdev@vger.kernel.org>, <davem@davemloft.net>
Cc: <kernel-team@fb.com>, <brouer@redhat.com>, <ilias.apalodimas@linaro.org>
Subject: [net-next PATCH v2 2/2] page_pool: remove hold/release count from tracepoints
Date: Thu, 14 Nov 2019 08:37:15 -0800 [thread overview]
Message-ID: <20191114163715.4184099-3-jonathan.lemon@gmail.com> (raw)
In-Reply-To: <20191114163715.4184099-1-jonathan.lemon@gmail.com>
When the last page is released from the page pool, it is possible
that the delayed removal thread sees inflight == 0, and frees the
pool. While the freed pointer is only copied by the tracepoint
and not dereferenced, it really isn't correct. Avoid this case by
reporting the page release before releasing the page.
This also removes a second atomic operation from the release path.
Signed-off-by: Jonathan Lemon <jonathan.lemon@gmail.com>
---
include/trace/events/page_pool.h | 24 ++++++++++--------------
net/core/page_pool.c | 8 +++++---
2 files changed, 15 insertions(+), 17 deletions(-)
diff --git a/include/trace/events/page_pool.h b/include/trace/events/page_pool.h
index 47b5ee880aa9..0adf9aed9f5b 100644
--- a/include/trace/events/page_pool.h
+++ b/include/trace/events/page_pool.h
@@ -35,50 +35,46 @@ TRACE_EVENT(page_pool_inflight,
__entry->pool, __entry->inflight, __entry->hold, __entry->release)
);
-TRACE_EVENT(page_pool_state_release,
+TRACE_EVENT(page_pool_page_release,
TP_PROTO(const struct page_pool *pool,
- const struct page *page, u32 release),
+ const struct page *page)
- TP_ARGS(pool, page, release),
+ TP_ARGS(pool, page),
TP_STRUCT__entry(
__field(const struct page_pool *, pool)
__field(const struct page *, page)
- __field(u32, release)
),
TP_fast_assign(
__entry->pool = pool;
__entry->page = page;
- __entry->release = release;
),
- TP_printk("page_pool=%p page=%p release=%u",
- __entry->pool, __entry->page, __entry->release)
+ TP_printk("page_pool=%p page=%p",
+ __entry->pool, __entry->page)
);
-TRACE_EVENT(page_pool_state_hold,
+TRACE_EVENT(page_pool_page_hold,
TP_PROTO(const struct page_pool *pool,
- const struct page *page, u32 hold),
+ const struct page *page),
- TP_ARGS(pool, page, hold),
+ TP_ARGS(pool, page),
TP_STRUCT__entry(
__field(const struct page_pool *, pool)
__field(const struct page *, page)
- __field(u32, hold)
),
TP_fast_assign(
__entry->pool = pool;
__entry->page = page;
- __entry->hold = hold;
),
- TP_printk("page_pool=%p page=%p hold=%u",
- __entry->pool, __entry->page, __entry->hold)
+ TP_printk("page_pool=%p page=%p",
+ __entry->pool, __entry->page)
);
#endif /* _TRACE_PAGE_POOL_H */
diff --git a/net/core/page_pool.c b/net/core/page_pool.c
index bfe96326335d..1e66341fdac8 100644
--- a/net/core/page_pool.c
+++ b/net/core/page_pool.c
@@ -163,7 +163,7 @@ static struct page *__page_pool_alloc_pages_slow(struct page_pool *pool,
/* Track how many pages are held 'in-flight' */
pool->pages_state_hold_cnt++;
- trace_page_pool_state_hold(pool, page, pool->pages_state_hold_cnt);
+ trace_page_pool_page_hold(pool, page);
/* When page just alloc'ed is should/must have refcnt 1. */
return page;
@@ -222,9 +222,11 @@ static void __page_pool_clean_page(struct page_pool *pool,
DMA_ATTR_SKIP_CPU_SYNC);
page->dma_addr = 0;
skip_dma_unmap:
+ trace_page_pool_page_release(pool, page);
+ /* This may be the last page returned, releasing the pool, so
+ * it is not safe to reference pool afterwards.
+ */
atomic_inc(&pool->pages_state_release_cnt);
- trace_page_pool_state_release(pool, page,
- atomic_read(&pool->pages_state_release_cnt));
}
/* unmap the page and clean our state */
--
2.17.1
next prev parent reply other threads:[~2019-11-14 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 16:37 [net-next PATCH v2 0/2] Change page_pool timeout handling Jonathan Lemon
2019-11-14 16:37 ` [net-next PATCH v2 1/2] page_pool: do not release pool until inflight == 0 Jonathan Lemon
2019-11-14 21:27 ` Jesper Dangaard Brouer
2019-11-14 16:37 ` Jonathan Lemon [this message]
2019-11-14 20:53 ` [net-next PATCH v2 2/2] page_pool: remove hold/release count from tracepoints kbuild test robot
2019-11-14 21:07 ` Jesper Dangaard Brouer
2019-11-14 21:56 ` Jonathan Lemon
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=20191114163715.4184099-3-jonathan.lemon@gmail.com \
--to=jonathan.lemon@gmail.com \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=ilias.apalodimas@linaro.org \
--cc=kernel-team@fb.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 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).