From: Simon Horman <horms@kernel.org>
To: Liang Chen <liangchen.linux@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, linyunsheng@huawei.com, hawk@kernel.org,
ilias.apalodimas@linaro.org, daniel@iogearbox.net,
ast@kernel.org, netdev@vger.kernel.org
Subject: Re: [RFC PATCH net-next v2 1/2] net: veth: Page pool creation error handling for existing pools only
Date: Tue, 1 Aug 2023 14:18:17 +0200 [thread overview]
Message-ID: <ZMj4CdJe7m25OlGj@kernel.org> (raw)
In-Reply-To: <20230801061932.10335-1-liangchen.linux@gmail.com>
On Tue, Aug 01, 2023 at 02:19:31PM +0800, Liang Chen wrote:
> The failure handling procedure destroys page pools for all queues,
> including those that haven't had their page pool created yet. this patch
> introduces necessary adjustments to prevent potential risks and
> inconsistency with the error handling behavior.
>
> Signed-off-by: Liang Chen <liangchen.linux@gmail.com>
I wonder if this should this have a fixes tag and be targeted at 'net' as a
bugfix?
next prev parent reply other threads:[~2023-08-01 12:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 6:19 [RFC PATCH net-next v2 1/2] net: veth: Page pool creation error handling for existing pools only Liang Chen
2023-08-01 6:19 ` [RFC PATCH net-next v2 2/2] net: veth: Improving page pool pages recycling Liang Chen
2023-08-02 12:32 ` Yunsheng Lin
2023-08-07 12:20 ` Liang Chen
2023-08-08 11:16 ` Yunsheng Lin
2023-08-09 10:01 ` Liang Chen
2023-08-09 12:35 ` Yunsheng Lin
2023-08-12 1:52 ` Liang Chen
2023-08-11 18:16 ` Jesper Dangaard Brouer
2023-08-12 2:02 ` Liang Chen
2023-08-01 12:18 ` Simon Horman [this message]
2023-08-11 11:56 ` [RFC PATCH net-next v2 1/2] net: veth: Page pool creation error handling for existing pools only Liang Chen
2023-08-02 8:56 ` Jesper Dangaard Brouer
2023-08-11 12:02 ` Liang Chen
2023-08-11 16:35 ` Jesper Dangaard Brouer
2023-08-12 2:16 ` Liang Chen
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=ZMj4CdJe7m25OlGj@kernel.org \
--to=horms@kernel.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=kuba@kernel.org \
--cc=liangchen.linux@gmail.com \
--cc=linyunsheng@huawei.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.