From: patchwork-bot+netdevbpf@kernel.org
To: Diogo Jahchan Koike <djahchankoike@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, christophe.leroy@csgroup.eu,
maxime.chevallier@bootlin.com,
syzbot+c641161e97237326ea74@syzkaller.appspotmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch net-next v2] net: fix unreleased lock in cable test
Date: Tue, 27 Aug 2024 20:10:30 +0000 [thread overview]
Message-ID: <172478943074.751194.1705934546816050259.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240826134656.94892-1-djahchankoike@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 26 Aug 2024 10:45:46 -0300 you wrote:
> fix an unreleased lock in out_dev_put path by removing the (now)
> unnecessary path.
>
> Reported-by: syzbot+c641161e97237326ea74@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=c641161e97237326ea74
> Fixes: 3688ff3077d3 ("net: ethtool: cable-test: Target the command to the requested PHY")
> Signed-off-by: Diogo Jahchan Koike <djahchankoike@gmail.com>
>
> [...]
Here is the summary with links:
- [net-next,v2] net: fix unreleased lock in cable test
https://git.kernel.org/netdev/net-next/c/3d6a0c4f4552
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:[~2024-08-27 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240826121435.88756-1-djahchankoike@gmail.com>
2024-08-26 13:45 ` [patch net-next v2] net: fix unreleased lock in cable test Diogo Jahchan Koike
2024-08-26 16:16 ` Maxime Chevallier
2024-08-27 20:10 ` 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=172478943074.751194.1705934546816050259.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=djahchankoike@gmail.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+c641161e97237326ea74@syzkaller.appspotmail.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