netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: hannes@stressinduktion.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/9] Introduce support to lazy initialize mostly static keys
Date: Sat, 19 Oct 2013 19:46:35 -0400 (EDT)	[thread overview]
Message-ID: <20131019.194635.2189923305870380269.davem@davemloft.net> (raw)
In-Reply-To: <1382212139-20301-1-git-send-email-hannes@stressinduktion.org>

From: Hannes Frederic Sowa <hannes@stressinduktion.org>
Date: Sat, 19 Oct 2013 21:48:50 +0200

> This series implements support for delaying the initialization of secret
> keys, e.g. used for hashing, for as long as possible. This functionality
> is implemented by a new macro, net_get_random_bytes.
> 
> I already used it to protect the socket hashes, the syncookie secret
> (most important) and the tcp_fastopen secrets.
> 
> Changelog:
> v2) Use static_keys in net_get_random_once to have as minimal impact to
>     the fast-path as possible.
> v3) added patch "static_key: WARN on usage before jump_label_init was called":
>     Patch "x86/jump_label: expect default_nop if static_key gets enabled
>     on boot-up" relaxes the checks for using static_key primitives before
>     jump_label_init. So tighten them first.
> v4) Update changelog on the patch "static_key: WARN on usage before
>     jump_label_init was called"

Although I was very skeptical about these changes when you first posted
them, I am quite happy with this series now.

Thanks for working on this and not giving up :-)

Series applied, thanks a lot!

  parent reply	other threads:[~2013-10-19 23:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-19 19:48 [PATCH net-next v4 0/9] Introduce support to lazy initialize mostly static keys Hannes Frederic Sowa
2013-10-19 19:48 ` [PATCH net-next v4 1/9] ipv4: split inet_ehashfn to hash functions per compilation unit Hannes Frederic Sowa
2013-10-19 19:48 ` [PATCH net-next v4 2/9] ipv6: split inet6_ehashfn " Hannes Frederic Sowa
2013-10-19 19:48 ` [PATCH net-next v4 3/9] static_key: WARN on usage before jump_label_init was called Hannes Frederic Sowa
2013-11-06 21:16   ` Steven Rostedt
2013-11-07  0:50     ` Hannes Frederic Sowa
2013-11-07  1:02       ` Steven Rostedt
2013-11-07  9:08         ` Ingo Molnar
2013-10-19 19:48 ` [PATCH net-next v4 4/9] x86/jump_label: expect default_nop if static_key gets enabled on boot-up Hannes Frederic Sowa
2013-10-19 19:48 ` [PATCH net-next v4 5/9] net: introduce new macro net_get_random_once Hannes Frederic Sowa
2013-10-19 19:48 ` [PATCH net-next v4 6/9] inet: split syncookie keys for ipv4 and ipv6 and initialize with net_get_random_once Hannes Frederic Sowa
2013-10-19 19:48 ` [PATCH net-next v4 7/9] inet: convert inet_ehash_secret and ipv6_hash_secret to net_get_random_once Hannes Frederic Sowa
2013-10-19 19:48 ` [PATCH net-next v4 8/9] tcp: switch tcp_fastopen key generation " Hannes Frederic Sowa
2013-10-19 19:48 ` [PATCH net-next v4 9/9] net: switch net_secret " Hannes Frederic Sowa
2013-10-19 23:46 ` David Miller [this message]
2013-10-20  3:33   ` [PATCH net-next v4 0/9] Introduce support to lazy initialize mostly static keys Hannes Frederic Sowa

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=20131019.194635.2189923305870380269.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=hannes@stressinduktion.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).