From: patchwork-bot+netdevbpf@kernel.org
To: Pavel Skripkin <paskripkin@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, andrew@lunn.ch,
michael@walle.cc, abrodkin@synopsys.com, talz@ezchip.com,
noamc@ezchip.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH 0/3] net: ethernat: ezchip: bug fixing and code improvments
Date: Sat, 19 Jun 2021 19:30:03 +0000 [thread overview]
Message-ID: <162413100353.3389.12147406077776982981.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1624032669.git.paskripkin@gmail.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Fri, 18 Jun 2021 19:14:23 +0300 you wrote:
> While manual code reviewing, I found some error in ezchip driver.
> Two of them looks very dangerous:
> 1. use-after-free in nps_enet_remove
> Accessing netdev private data after free_netdev()
>
> 2. wrong error handling of platform_get_irq()
> It can cause passing negative irq to request_irq()
>
> [...]
Here is the summary with links:
- [1/3] net: ethernet: ezchip: fix UAF in nps_enet_remove
https://git.kernel.org/netdev/net/c/e4b8700e07a8
- [2/3] net: ethernet: ezchip: remove redundant check
https://git.kernel.org/netdev/net/c/4ae85b23e1f0
- [3/3] net: ethernet: ezchip: fix error handling
https://git.kernel.org/netdev/net/c/0de449d59959
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:[~2021-06-19 19:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 16:14 [PATCH 0/3] net: ethernat: ezchip: bug fixing and code improvments Pavel Skripkin
2021-06-18 16:14 ` [PATCH 1/3] net: ethernet: ezchip: fix UAF in nps_enet_remove Pavel Skripkin
2021-06-18 16:14 ` [PATCH 2/3] net: ethernet: ezchip: remove redundant check Pavel Skripkin
2021-06-18 16:14 ` [PATCH 3/3] net: ethernet: ezchip: fix error handling Pavel Skripkin
2021-06-19 19:30 ` 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=162413100353.3389.12147406077776982981.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=abrodkin@synopsys.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=noamc@ezchip.com \
--cc=paskripkin@gmail.com \
--cc=talz@ezchip.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