From: patchwork-bot+netdevbpf@kernel.org
To: David Ahern <dsahern@kernel.org>
Cc: kuba@kernel.org, davem@davemloft.net, pabeni@redhat.com,
netdev@vger.kernel.org, idosch@idosch.org, exsociety@gmail.com
Subject: Re: [PATCH v3 net] ipv4: Handle attempt to delete multipath route when fib_info contains an nh reference
Date: Fri, 07 Oct 2022 07:50:15 +0000 [thread overview]
Message-ID: <166512901590.847.15819501464797229185.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221006164849.9386-1-dsahern@kernel.org>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 6 Oct 2022 10:48:49 -0600 you wrote:
> Gwangun Jung reported a slab-out-of-bounds access in fib_nh_match:
> fib_nh_match+0xf98/0x1130 linux-6.0-rc7/net/ipv4/fib_semantics.c:961
> fib_table_delete+0x5f3/0xa40 linux-6.0-rc7/net/ipv4/fib_trie.c:1753
> inet_rtm_delroute+0x2b3/0x380 linux-6.0-rc7/net/ipv4/fib_frontend.c:874
>
> Separate nexthop objects are mutually exclusive with the legacy
> multipath spec. Fix fib_nh_match to return if the config for the
> to be deleted route contains a multipath spec while the fib_info
> is using a nexthop object.
>
> [...]
Here is the summary with links:
- [v3,net] ipv4: Handle attempt to delete multipath route when fib_info contains an nh reference
https://git.kernel.org/netdev/net/c/61b91eb33a69
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:[~2022-10-07 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 16:48 [PATCH v3 net] ipv4: Handle attempt to delete multipath route when fib_info contains an nh reference David Ahern
2022-10-06 20:29 ` Ido Schimmel
2022-10-07 7:50 ` 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=166512901590.847.15819501464797229185.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=exsociety@gmail.com \
--cc=idosch@idosch.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.