From: Vladimir Oltean <olteanv@gmail.com>
To: "Radu Nicolae Pirea (OSS)" <radu-nicolae.pirea@oss.nxp.com>
Cc: gregkh@linuxfoundation.org, netdev@vger.kernel.org,
stable@vger.kernel.org, linux-kernel@vger.kernel.org,
andrew@lunn.ch, pabeni@redhat.com, kuba@kernel.org,
edumazet@google.com, davem@davemloft.net, f.fainelli@gmail.com,
Radu Pirea <radu-nicolae.pirea@nxp.com>
Subject: Re: [PATCH] net: dsa: sja1105: fix slab-out-of-bounds in sja1105_setup
Date: Tue, 6 Dec 2022 17:26:30 +0200 [thread overview]
Message-ID: <20221206152630.lypso2kbh6gwwlse@skbuf> (raw)
In-Reply-To: <20221206151136.802344-1-radu-nicolae.pirea@oss.nxp.com>
On Tue, Dec 06, 2022 at 05:11:36PM +0200, Radu Nicolae Pirea (OSS) wrote:
> From: Radu Pirea <radu-nicolae.pirea@nxp.com>
>
> Fix slab-out-of-bounds in sja1105_setup.
>
> Signed-off-by: Radu Pirea <radu-nicolae.pirea@nxp.com>
> ---
> drivers/net/dsa/sja1105/sja1105_main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Can be applied on top of 5.15.81 stable branch.
Here the backporting process has to work differently.
Since the fixed code is also present in the master branch of the tree
responsible with bug fixes for this code area
(https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git), you
have to base your patch on that tree, and send the patch to be applied
by the netdev maintainers, not by stable directly. You do that by using
git send-email --subject-prefix "PATCH v2 net". You also don't CC stable
and Greg, just the networking people from ./scripts/get_maintainer.pl.
After a while, the patch will land automatically in stable, through the
"net" tree.
You must also add this above your Signed-off-by tag:
Fixes: 38fbe91f2287 ("net: dsa: sja1105: configure the multicast policers, if present")
next prev parent reply other threads:[~2022-12-06 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 15:11 Radu Nicolae Pirea (OSS)
2022-12-06 15:26 ` Vladimir Oltean [this message]
2022-12-06 16:06 ` Greg KH
2022-12-06 16:25 ` Vladimir Oltean
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=20221206152630.lypso2kbh6gwwlse@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=radu-nicolae.pirea@nxp.com \
--cc=radu-nicolae.pirea@oss.nxp.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
all inboxes | Powered by JetHome®