From: Jakub Kicinski <kuba@kernel.org>
To: Jakub Raczynski <j.raczynski@samsung.com>
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
mcoquelin.stm32@gmail.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH net v3 0/2] net/stmmac: Secure against failures of DMA memory allocation
Date: Thu, 23 Jul 2026 07:23:52 -0700 [thread overview]
Message-ID: <20260723072352.6db4df7f@kernel.org> (raw)
In-Reply-To: <20260715123602.51950-1-j.raczynski@samsung.com>
On Wed, 15 Jul 2026 14:36:00 +0200 Jakub Raczynski wrote:
> This series fixing two issues related to fails of
> __alloc_dma_rx_desc_resources(). Original issue from 1st patch is related to
> page_pool that has happened in testing env, while second was requested by
> Sashiko to have similar change for DMA allocation.
> To have complete fix for all failures of __alloc_dma_rx_desc_resources(),
> merge two fixes into series.
Clashiko is not impressed by the second patch.
Is it possible to avoid calling the functions in semi-consistent state?
--
pw-bot: cr
next prev parent reply other threads:[~2026-07-23 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260715123609eucas1p276498c4701060ffbb6789cb096696a31@eucas1p2.samsung.com>
2026-07-15 12:36 ` [PATCH net v3 0/2] net/stmmac: Secure against failures of DMA memory allocation Jakub Raczynski
2026-07-15 12:36 ` [PATCH net v3 1/2] net/stmmac: Set Rx queue page_pool to NULL when freeing DMA resources Jakub Raczynski
2026-07-15 18:05 ` Mina Almasry
2026-07-15 12:36 ` [PATCH net v3 2/2] net/stmmac: Prevent dma queue NULL free on allocation failure Jakub Raczynski
2026-07-23 14:23 ` Jakub Kicinski [this message]
2026-07-23 15:24 ` [PATCH net v3 0/2] net/stmmac: Secure against failures of DMA memory allocation Jakub Raczynski
2026-07-23 17:21 ` Jakub Kicinski
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=20260723072352.6db4df7f@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=j.raczynski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--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 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.