From: patchwork-bot+netdevbpf@kernel.org
To: Niels Dossche <dossche.niels@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
yoshfuji@linux-ipv6.org, dsahern@kernel.org, kuba@kernel.org,
niels.dossche@ugent.be
Subject: Re: [PATCH net v2] ipv6: prevent a possible race condition with lifetimes
Date: Thu, 24 Feb 2022 17:20:10 +0000 [thread overview]
Message-ID: <164572321046.7006.13558166524967233977.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220223131954.6570-1-niels.dossche@ugent.be>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 23 Feb 2022 14:19:56 +0100 you wrote:
> valid_lft, prefered_lft and tstamp are always accessed under the lock
> "lock" in other places. Reading these without taking the lock may result
> in inconsistencies regarding the calculation of the valid and preferred
> variables since decisions are taken on these fields for those variables.
>
> Signed-off-by: Niels Dossche <dossche.niels@gmail.com>
> Reviewed-by: David Ahern <dsahern@kernel.org>
> Signed-off-by: Niels Dossche <niels.dossche@ugent.be>
>
> [...]
Here is the summary with links:
- [net,v2] ipv6: prevent a possible race condition with lifetimes
https://git.kernel.org/netdev/net/c/6c0d8833a605
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-02-24 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 13:19 [PATCH net v2] ipv6: prevent a possible race condition with lifetimes Niels Dossche
2022-02-24 17:20 ` 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=164572321046.7006.13558166524967233977.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dossche.niels@gmail.com \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=niels.dossche@ugent.be \
--cc=yoshfuji@linux-ipv6.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 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.