From: patchwork-bot+netdevbpf@kernel•org
To: =?utf-8?b?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2VuIDx0b2tlQHJlZGhhdC5jb20+?=@ci•codeaurora.org
Cc: grygorii.strashko@ti•com, ilias.apalodimas@linaro•org,
m-karicheri2@ti•com, davem@davemloft•net, brouer@redhat•com,
ivan.khoronzhuk@linaro•org, alexei.starovoitov@gmail•com,
colin.foster@in-advantage•com, kuba@kernel•org,
linux-omap@vger•kernel.org, netdev@vger•kernel.org
Subject: Re: [PATCH net] net: cpsw: Properly initialise struct page_pool_params
Date: Tue, 25 Jan 2022 16:46:14 +0000 [thread overview]
Message-ID: <164312917415.15904.320238953994313233.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220124143531.361005-1-toke@redhat.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft•net>:
On Mon, 24 Jan 2022 15:35:29 +0100 you wrote:
> The cpsw driver didn't properly initialise the struct page_pool_params
> before calling page_pool_create(), which leads to crashes after the struct
> has been expanded with new parameters.
>
> The second Fixes tag below is where the buggy code was introduced, but
> because the code was moved around this patch will only apply on top of the
> commit in the first Fixes tag.
>
> [...]
Here is the summary with links:
- [net] net: cpsw: Properly initialise struct page_pool_params
https://git.kernel.org/netdev/net/c/c63003e3d997
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-01-25 16:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 14:35 [PATCH net] net: cpsw: Properly initialise struct page_pool_params Toke Høiland-Jørgensen
2022-01-24 18:51 ` Colin Foster
2022-01-25 5:15 ` Colin Foster
2022-01-25 10:22 ` Toke Høiland-Jørgensen
2022-01-25 8:48 ` Jesper Dangaard Brouer
2022-01-25 16:46 ` patchwork-bot+netdevbpf [this message]
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=164312917415.15904.320238953994313233.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc==?utf-8?b?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2VuIDx0b2tlQHJlZGhhdC5jb20+?=@ci$(echo .)codeaurora.org \
--cc=alexei.starovoitov@gmail$(echo .)com \
--cc=brouer@redhat$(echo .)com \
--cc=colin.foster@in-advantage$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=grygorii.strashko@ti$(echo .)com \
--cc=ilias.apalodimas@linaro$(echo .)org \
--cc=ivan.khoronzhuk@linaro$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-omap@vger$(echo .)kernel.org \
--cc=m-karicheri2@ti$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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