Netdev List
 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 net-next 0/4] tcp: listener refactor part 16
Date: Tue, 24 Mar 2015 15:14:39 -0400 (EDT)	[thread overview]
Message-ID: <20150324.151439.133059567496002449.davem@davemloft.net> (raw)
In-Reply-To: <20150324.150257.1215806444155190560.davem@davemloft.net>

From: David Miller <davem@davemloft.net>
Date: Tue, 24 Mar 2015 15:02:57 -0400 (EDT)

> From: Eric Dumazet <edumazet@google.com>
> Date: Mon, 23 Mar 2015 21:34:22 -0700
> 
>> 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, keep up the good work Eric.

Actually, I have to back this out.

You can't mark all of these things const, because of lockdep:

kernel/Makefile:133: *** No X.509 certificates found ***
net/ipv4/tcp_ipv4.c: In function ‘tcp_md5_do_lookup’:
net/ipv4/tcp_ipv4.c:907:2: warning: passing argument 1 of ‘lock_is_held’ discards ‘const’ qualifier from pointer target type [enabled by default]
In file included from include/linux/spinlock_types.h:18:0,
                 from include/linux/spinlock.h:81,
                 from include/linux/seqlock.h:35,
                 from include/linux/time.h:5,
                 from include/linux/stat.h:18,
                 from include/linux/module.h:10,
                 from net/ipv4/tcp_ipv4.c:58:
include/linux/lockdep.h:341:12: note: expected ‘struct lockdep_map *’ but argument is of type ‘const struct lockdep_map *’

  reply	other threads:[~2015-03-24 19:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24  4:34 [PATCH net-next 0/4] tcp: listener refactor part 16 Eric Dumazet
2015-03-24  4:34 ` [PATCH net-next 1/4] tcp: use C99 initializers in new_state[] Eric Dumazet
2015-03-24  4:34 ` [PATCH net-next 2/4] tcp: md5: input path is run under rcu protected sections Eric Dumazet
2015-03-24  4:34 ` [PATCH net-next 3/4] tcp: md5: remove request sock argument of calc_md5_hash() Eric Dumazet
2015-03-24  4:34 ` [PATCH net-next 4/4] tcp: md5: get rid of tcp_v[46]_reqsk_md5_lookup() Eric Dumazet
2015-03-24 19:02 ` [PATCH net-next 0/4] tcp: listener refactor part 16 David Miller
2015-03-24 19:14   ` David Miller [this message]
2015-03-24 21:28     ` Eric Dumazet

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.151439.133059567496002449.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