From: Sven Eckelmann <sven@narfation.org>
To: Marek Lindner <mareklindner@neomailbox.ch>,
Simon Wunderlich <sw@simonwunderlich.de>,
Antonio Quartulli <a@unstable.cc>,
Remi Pommarel <repk@triplefau.lt>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
b.a.t.m.a.n@lists.open-mesh.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Remi Pommarel <repk@triplefau.lt>
Subject: Re: [PATCH net] batman-adv: Do not get eth header before batadv_check_management_packet
Date: Fri, 28 Jul 2023 15:49:46 +0200 [thread overview]
Message-ID: <10396914.nUPlyArG6x@sven-l14> (raw)
In-Reply-To: <20230728133850.5974-1-repk@triplefau.lt>
[-- Attachment #1: Type: text/plain, Size: 648 bytes --]
On Fri, 28 Jul 2023 15:38:50 +0200, Remi Pommarel wrote:
> If received skb in batadv_v_elp_packet_recv or batadv_v_ogm_packet_recv
> is either cloned or non linearized then its data buffer will be
> reallocated by batadv_check_management_packet when skb_cow or
> skb_linearize get called. Thus geting ethernet header address inside
> skb data buffer before batadv_check_management_packet had any chance to
> reallocate it could lead to the following kernel panic:
>
> [...]
Applied, thanks!
[1/1] batman-adv: Do not get eth header before batadv_check_management_packet
commit: eac27a41ab641de074655d2932fc7f8cdb446881
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-07-28 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 13:38 [PATCH net] batman-adv: Do not get eth header before batadv_check_management_packet Remi Pommarel
2023-07-28 13:49 ` Sven Eckelmann [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=10396914.nUPlyArG6x@sven-l14 \
--to=sven@narfation.org \
--cc=a@unstable.cc \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mareklindner@neomailbox.ch \
--cc=netdev@vger.kernel.org \
--cc=repk@triplefau.lt \
--cc=stable@vger.kernel.org \
--cc=sw@simonwunderlich.de \
/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