From: patchwork-bot+netdevbpf@kernel.org
To: Nikita Zhandarovich <n.zhandarovich@fintech.ru>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, r-gunasekaran@ti.com, horms@kernel.org,
wojciech.drewek@intel.com, m-karicheri2@ti.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org,
syzbot+3ae0a3f42c84074b7c8e@syzkaller.appspotmail.com
Subject: Re: [PATCH net] net: hsr: remove WARN_ONCE() in send_hsr_supervision_frame()
Date: Mon, 29 Jan 2024 11:30:26 +0000 [thread overview]
Message-ID: <170652782699.19974.1569305900184151152.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240124102147.14081-1-n.zhandarovich@fintech.ru>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 24 Jan 2024 02:21:47 -0800 you wrote:
> Syzkaller reported [1] hitting a warning after failing to allocate
> resources for skb in hsr_init_skb(). Since a WARN_ONCE() call will
> not help much in this case, it might be prudent to switch to
> netdev_warn_once(). At the very least it will suppress syzkaller
> reports such as [1].
>
> Just in case, use netdev_warn_once() in send_prp_supervision_frame()
> for similar reasons.
>
> [...]
Here is the summary with links:
- [net] net: hsr: remove WARN_ONCE() in send_hsr_supervision_frame()
https://git.kernel.org/netdev/net/c/37e8c97e5390
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-01-29 11:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 10:21 [PATCH net] net: hsr: remove WARN_ONCE() in send_hsr_supervision_frame() Nikita Zhandarovich
2024-01-29 11: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=170652782699.19974.1569305900184151152.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=m-karicheri2@ti.com \
--cc=n.zhandarovich@fintech.ru \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=r-gunasekaran@ti.com \
--cc=syzbot+3ae0a3f42c84074b7c8e@syzkaller.appspotmail.com \
--cc=wojciech.drewek@intel.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;
as well as URLs for NNTP newsgroup(s).