From: Eric Dumazet <dada1@cosmosbay.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
fbl@redhat.com, nhorman@redhat.com, davem@redhat.com,
oleg@redhat.com
Subject: Re: [RFC] tcp: race in receive part
Date: Thu, 25 Jun 2009 12:46:43 +0200 [thread overview]
Message-ID: <4A435593.1050806@cosmosbay.com> (raw)
In-Reply-To: <4A435162.90109@gmail.com>
Eric Dumazet a écrit :
> Jiri Olsa a écrit :
>> I made the modification, plz check the attached diff.
>>
>> I found some places where the read_lock is not ahead of the check:
>> "if (sk->sk_sleep && waitqueue_active(sk->sk_sleep))"
>>
>> I'm not sure we dont want to address those as well; located in following
>> files:
>> drivers/net/tun.c
>> net/core/stream.c
>> net/sctp/socket.c
>> net/sunrpc/svcsock.c
>
> We'll take care of them later :)
>
>>
>> thanks,
>> jirka
>>
>
> This patch is OK with me, please submit a new formal patch with
> fresh ChangeLog so that we can all agree and Signed-off-by/Acked-by
>
> Oleg, I think your comment can be addressed in a followup patch ?
>
> Thanks to all
To clarify, I meant the second comment from Oleg.
Jiri, please define a "smp_mb__after_lock()" instead of smp_mb__after_read_lock()
+/* The {read|write|spin}_lock() on x86 are full memory barriers. */
+#define smp_mb__after_lock() do { } while (0)
+
prev parent reply other threads:[~2009-06-25 10:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 10:27 [RFC] tcp: race in receive part Jiri Olsa
2009-06-18 14:06 ` Eric Dumazet
2009-06-23 9:12 ` Jiri Olsa
2009-06-23 10:32 ` Eric Dumazet
2009-06-23 19:44 ` Oleg Nesterov
2009-06-24 10:20 ` Jiri Olsa
2009-06-24 11:04 ` Eric Dumazet
2009-06-24 16:21 ` Jiri Olsa
2009-06-24 16:30 ` Oleg Nesterov
2009-06-24 16:41 ` Oleg Nesterov
2009-06-25 10:51 ` Eric Dumazet
2009-06-25 10:28 ` Eric Dumazet
2009-06-25 10:46 ` Eric Dumazet [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=4A435593.1050806@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=davem@redhat.com \
--cc=fbl@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=oleg@redhat.com \
/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).