From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
dsahern@kernel.org, netdev@vger.kernel.org,
eric.dumazet@gmail.com,
syzbot+c15aa445274af8674f41@syzkaller.appspotmail.com,
thinker.li@gmail.com
Subject: Re: [PATCH net-next] ipv6: do not check fib6_has_expires() in fib6_info_release()
Date: Sat, 09 Dec 2023 01:30:23 +0000 [thread overview]
Message-ID: <170208542393.22393.12653821622545796367.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231207201322.549000-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 7 Dec 2023 20:13:22 +0000 you wrote:
> My prior patch went a bit too far, because apparently fib6_has_expires()
> could be true while f6i->gc_link is not hashed yet.
>
> fib6_set_expires_locked() can indeed set RTF_EXPIRES
> while f6i->fib6_table is NULL.
>
> Original syzbot reports were about corruptions caused
> by dangling f6i->gc_link.
>
> [...]
Here is the summary with links:
- [net-next] ipv6: do not check fib6_has_expires() in fib6_info_release()
https://git.kernel.org/netdev/net-next/c/a3c205d0560f
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:[~2023-12-09 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 20:13 [PATCH net-next] ipv6: do not check fib6_has_expires() in fib6_info_release() Eric Dumazet
2023-12-07 20:25 ` David Ahern
2023-12-07 20:27 ` Kui-Feng Lee
2023-12-09 1: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=170208542393.22393.12653821622545796367.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+c15aa445274af8674f41@syzkaller.appspotmail.com \
--cc=thinker.li@gmail.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.