From: Greg KH <gregkh@linuxfoundation.org>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: ast@kernel.org, daniel@iogearbox.net, davem@davemloft.net,
kuba@kernel.org, netdev@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net] net: handle ARPHRD_PIMREG in dev_is_mac_header_xmit()
Date: Tue, 15 Mar 2022 10:15:34 +0100 [thread overview]
Message-ID: <YjBZNmRqp/GODOSP@kroah.com> (raw)
In-Reply-To: <20220315090102.31091-1-nicolas.dichtel@6wind.com>
On Tue, Mar 15, 2022 at 10:01:02AM +0100, Nicolas Dichtel wrote:
> This kind of interface doesn't have a mac header. This patch fixes
> bpf_redirect() to a PIM interface.
>
> Fixes: 27b29f63058d ("bpf: add bpf_redirect() helper")
> Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
> ---
> include/linux/if_arp.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/linux/if_arp.h b/include/linux/if_arp.h
> index b712217f7030..1ed52441972f 100644
> --- a/include/linux/if_arp.h
> +++ b/include/linux/if_arp.h
> @@ -52,6 +52,7 @@ static inline bool dev_is_mac_header_xmit(const struct net_device *dev)
> case ARPHRD_VOID:
> case ARPHRD_NONE:
> case ARPHRD_RAWIP:
> + case ARPHRD_PIMREG:
> return false;
> default:
> return true;
> --
> 2.33.0
>
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
next prev parent reply other threads:[~2022-03-15 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 9:01 [PATCH net] net: handle ARPHRD_PIMREG in dev_is_mac_header_xmit() Nicolas Dichtel
2022-03-15 9:15 ` Greg KH [this message]
2022-03-15 9:20 ` [PATCH net v2] " Nicolas Dichtel
2022-03-17 4:30 ` patchwork-bot+netdevbpf
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=YjBZNmRqp/GODOSP@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=stable@vger.kernel.org \
/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).