From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: <netdev@vger.kernel.org>,
Jesper Dangaard Brouer <hawk@kernel.org>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH net-next] net: page_pool: fix warning code
Date: Fri, 5 Jul 2024 14:32:23 +0200 [thread overview]
Message-ID: <50291617-0872-4ba9-8ca5-329597a0eff5@intel.com> (raw)
In-Reply-To: <20240705134221.2f4de205caa1.I28496dc0f2ced580282d1fb892048017c4491e21@changeid>
From: Johannes Berg <johannes@sipsolutions.net>
Date: Fri, 5 Jul 2024 13:42:06 +0200
> From: Johannes Berg <johannes.berg@intel.com>
>
> WARN_ON_ONCE("string") doesn't really do what appears to
> be intended, so fix that.
>
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
"Fixes:" tag?
> ---
> net/core/page_pool.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/core/page_pool.c b/net/core/page_pool.c
> index 3927a0a7fa9a..97914a9e2a85 100644
> --- a/net/core/page_pool.c
> +++ b/net/core/page_pool.c
> @@ -445,7 +445,7 @@ static bool page_pool_dma_map(struct page_pool *pool, struct page *page)
> return true;
>
> unmap_failed:
> - WARN_ON_ONCE("unexpected DMA address, please report to netdev@");
> + WARN_ONCE(1, "unexpected DMA address, please report to netdev@");
> dma_unmap_page_attrs(pool->p.dev, dma,
> PAGE_SIZE << pool->p.order, pool->p.dma_dir,
> DMA_ATTR_SKIP_CPU_SYNC | DMA_ATTR_WEAK_ORDERING);
Thanks,
Olek
next prev parent reply other threads:[~2024-07-05 12:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 11:42 [PATCH net-next] net: page_pool: fix warning code Johannes Berg
2024-07-05 12:32 ` Alexander Lobakin [this message]
2024-07-05 12:33 ` Johannes Berg
2024-07-05 12:37 ` Alexander Lobakin
2024-07-05 12:39 ` Johannes Berg
2024-07-05 13:14 ` Przemek Kitszel
2024-07-05 13:28 ` Alexander Lobakin
2024-07-05 13:38 ` Przemek Kitszel
2024-07-05 14:19 ` Andrew Lunn
2024-07-05 14:23 ` Johannes Berg
2024-07-05 14:33 ` Alexander Lobakin
2024-07-05 14:36 ` Johannes Berg
2024-07-05 14:44 ` Alexander Lobakin
2024-07-09 3:40 ` 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=50291617-0872-4ba9-8ca5-329597a0eff5@intel.com \
--to=aleksander.lobakin@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@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