[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <160589940705.22082.10268101858431094788.git-patchwork-notify@kernel.org>
Date: Fri, 20 Nov 2020 19:10:07 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Colin King <colin.king@...onical.com>
Cc: sgoutham@...vell.com, lcherian@...vell.com, gakula@...vell.com,
jerinj@...vell.com, davem@...emloft.net, kuba@...nel.org,
naveenm@...vell.com, sbhatta@...vell.com, netdev@...r.kernel.org,
kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH][next] octeontx2-af: Fix access of iter->entry after iter
object has been kfree'd
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Wed, 18 Nov 2020 14:38:03 +0000 you wrote:
> From: Colin Ian King <colin.king@...onical.com>
>
> The call to pc_delete_flow can kfree the iter object, so the following
> dev_err message that accesses iter->entry can accessmemory that has
> just been kfree'd. Fix this by adding a temporary variable 'entry'
> that has a copy of iter->entry and also use this when indexing into
> the array mcam->entry2target_pffunc[]. Also print the unsigned value
> using the %u format specifier rather than %d.
>
> [...]
Here is the summary with links:
- [next] octeontx2-af: Fix access of iter->entry after iter object has been kfree'd
https://git.kernel.org/netdev/net-next/c/76483980174c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists