All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
	edumazet@google.com, w@1wt.eu, kman001@ucr.edu
Subject: Re: [PATCH net 0/2] inet: use siphash in exception handling
Date: Thu, 26 Aug 2021 09:30:06 +0000	[thread overview]
Message-ID: <162997020661.28182.14261277414825954591.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210825231729.401676-1-eric.dumazet@gmail.com>

Hello:

This series was applied to netdev/net.git (refs/heads/master):

On Wed, 25 Aug 2021 16:17:27 -0700 you wrote:
> From: Eric Dumazet <edumazet@google.com>
> 
> A group of security researchers brought to our attention
> the weakness of hash functions used in rt6_exception_hash()
> and fnhe_hashfun()
> 
> I made two distinct patches to help backports, since IPv6
> part was added in 4.15
> 
> [...]

Here is the summary with links:
  - [net,1/2] ipv6: use siphash in rt6_exception_hash()
    https://git.kernel.org/netdev/net/c/4785305c05b2
  - [net,2/2] ipv4: use siphash instead of Jenkins in fnhe_hashfun()
    https://git.kernel.org/netdev/net/c/6457378fe796

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-08-26  9:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-25 23:17 [PATCH net 0/2] inet: use siphash in exception handling Eric Dumazet
2021-08-25 23:17 ` [PATCH net 1/2] ipv6: use siphash in rt6_exception_hash() Eric Dumazet
2021-08-26  0:11   ` Wei Wang
2021-08-25 23:17 ` [PATCH net 2/2] ipv4: use siphash instead of Jenkins in fnhe_hashfun() Eric Dumazet
2021-08-26  9: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=162997020661.28182.14261277414825954591.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=kman001@ucr.edu \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=w@1wt.eu \
    /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.