From: Colin Foster <colin.foster@in-advantage.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Cc: "Toke Høiland-Jørgensen" <toke@redhat.com>,
"John Fastabend" <john.fastabend@gmail.com>,
"Alexei Starovoitov" <ast@kernel.org>,
"Jakub Kicinski" <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
"Jesper Dangaard Brouer" <hawk@kernel.org>
Subject: [net RFC v1 0/1] Fix NULL pointer dereference in page_pool
Date: Fri, 21 Jan 2022 16:56:43 -0800 [thread overview]
Message-ID: <20220122005644.802352-1-colin.foster@in-advantage.com> (raw)
I'm not sure if there's something wrong with my config, but as soon as I
run "ip link set eth0 up" I would get a crash that would invoke a
seemingly endless memory dump.
git bisect led me to the page_pool, where there isn't the existence of
page_pool_params inside of the pool. Therefore the check of
if (pool->p.init_callback) would cause a crash.
I have some out-of-tree patches currently, so I'm not sure if my case is
valid. Specifically the MTU of cpsw_new has been updated to 1520 to
account for my setup (beaglebone with eth0 as the CPU port of a DSA).
I'm also not familiar with much of net/core.
If it is valid that page_pool might not have page_pool_params in a DSA
scenario, then hopefully this patch is sufficient. If it isn't valid and
something I'm doing is invoking a memory issue - then I've got my work
cut out for me :-)
Colin Foster (1):
page_pool: fix NULL dereference crash
net/core/page_pool.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.25.1
next reply other threads:[~2022-01-22 0:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 0:56 Colin Foster [this message]
2022-01-22 0:56 ` [net RFC v1 1/1] page_pool: fix NULL dereference crash Colin Foster
2022-01-22 1:13 ` Alexei Starovoitov
2022-01-22 2:20 ` Colin Foster
2022-01-22 2:47 ` Alexei Starovoitov
2022-01-24 12:12 ` Toke Høiland-Jørgensen
2022-01-22 2:40 ` Colin Foster
2022-01-22 8:31 ` Jesper Dangaard Brouer
2022-01-22 19:46 ` Colin Foster
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=20220122005644.802352-1-colin.foster@in-advantage.com \
--to=colin.foster@in-advantage.com \
--cc=ast@kernel.org \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=toke@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
all inboxes | Powered by JetHome®