linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: George McCollister <george.mccollister@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	m-karicheri2@ti.com, ap420073@gmail.com, olteanv@gmail.com,
	kurt@linutronix.de, luc.vanoostenryck@gmail.com,
	wanghai38@huawei.com, phil@philpotter.co.uk,
	andreas.oetken@siemens.com, marco.wenzel@a-eberle.de,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: hsr: fix mac_len checks
Date: Mon, 24 May 2021 21:30:10 +0000	[thread overview]
Message-ID: <162189181017.16512.13935059871261299091.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210524185054.65642-1-george.mccollister@gmail.com>

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Mon, 24 May 2021 13:50:54 -0500 you wrote:
> Commit 2e9f60932a2c ("net: hsr: check skb can contain struct hsr_ethhdr
> in fill_frame_info") added the following which resulted in -EINVAL
> always being returned:
> 	if (skb->mac_len < sizeof(struct hsr_ethhdr))
> 		return -EINVAL;
> 
> mac_len was not being set correctly so this check completely broke
> HSR/PRP since it was always 14, not 20.
> 
> [...]

Here is the summary with links:
  - [net] net: hsr: fix mac_len checks
    https://git.kernel.org/netdev/net/c/48b491a5cc74

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-05-24 21:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24 18:50 [PATCH net] net: hsr: fix mac_len checks George McCollister
2021-05-24 21:29 ` Vladimir Oltean
2021-05-25 21:46   ` George McCollister
2021-05-24 21: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=162189181017.16512.13935059871261299091.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andreas.oetken@siemens.com \
    --cc=ap420073@gmail.com \
    --cc=davem@davemloft.net \
    --cc=george.mccollister@gmail.com \
    --cc=kuba@kernel.org \
    --cc=kurt@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    --cc=m-karicheri2@ti.com \
    --cc=marco.wenzel@a-eberle.de \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=phil@philpotter.co.uk \
    --cc=wanghai38@huawei.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).