public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: edumazet@google.com
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH v2 net-next 0/5] tcp: listener refactor part 16
Date: Tue, 24 Mar 2015 21:18:32 -0400 (EDT)	[thread overview]
Message-ID: <20150324.211832.684336006405198659.davem@davemloft.net> (raw)
In-Reply-To: <1427237936-19030-1-git-send-email-edumazet@google.com>

From: Eric Dumazet <edumazet@google.com>
Date: Tue, 24 Mar 2015 15:58:51 -0700

> A CONFIG_PROVE_RCU=y build revealed an RCU splat I had to fix.
> 
> I added const qualifiers to various md5 methods, as I expect
> to call them on behalf of request sock traffic even if
> the listener socket is not locked. This seems ok, but adding
> const makes the contract clearer. Note a good reduction
> of code size thanks to request/establish sockets convergence.

Series applied, thanks Eric.

      parent reply	other threads:[~2015-03-25  1:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 22:58 [PATCH v2 net-next 0/5] tcp: listener refactor part 16 Eric Dumazet
2015-03-24 22:58 ` [PATCH v2 net-next 1/5] tcp: md5: fix rcu lockdep splat Eric Dumazet
2015-03-24 22:58 ` [PATCH v2 net-next 2/5] tcp: use C99 initializers in new_state[] Eric Dumazet
2015-03-24 22:58 ` [PATCH v2 net-next 3/5] tcp: md5: input path is run under rcu protected sections Eric Dumazet
2015-03-24 22:58 ` [PATCH v2 net-next 4/5] tcp: md5: remove request sock argument of calc_md5_hash() Eric Dumazet
2015-03-24 22:58 ` [PATCH v2 net-next 5/5] tcp: md5: get rid of tcp_v[46]_reqsk_md5_lookup() Eric Dumazet
2015-03-25  1:18 ` David Miller [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=20150324.211832.684336006405198659.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --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