From: Daniel Borkmann <dborkman@redhat.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-sctp@vger.kernel.org, Vlad Yasevich <vyasevic@redhat.com>
Subject: Re: [PATCH net v2] net: sctp: test if association is dead in sctp_wake_up_waiters
Date: Wed, 09 Apr 2014 13:34:25 +0000 [thread overview]
Message-ID: <53454C61.70007@redhat.com> (raw)
In-Reply-To: <20140409105908.GC13412@hmsreliant.think-freely.org>
On 04/09/2014 12:59 PM, Neil Horman wrote:
...
> Both to the patch, and the documentation, as its not at all clear what lock
> protects the reading and writing of the dead variable.
Agreed, I'll send a v3 with an improved commit message to
summarize everything for future reference. Thanks everyone.
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Borkmann <dborkman@redhat.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-sctp@vger.kernel.org, Vlad Yasevich <vyasevic@redhat.com>
Subject: Re: [PATCH net v2] net: sctp: test if association is dead in sctp_wake_up_waiters
Date: Wed, 09 Apr 2014 15:34:25 +0200 [thread overview]
Message-ID: <53454C61.70007@redhat.com> (raw)
In-Reply-To: <20140409105908.GC13412@hmsreliant.think-freely.org>
On 04/09/2014 12:59 PM, Neil Horman wrote:
...
> Both to the patch, and the documentation, as its not at all clear what lock
> protects the reading and writing of the dead variable.
Agreed, I'll send a v3 with an improved commit message to
summarize everything for future reference. Thanks everyone.
next prev parent reply other threads:[~2014-04-09 13:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 23:32 [PATCH net v2] net: sctp: test if association is dead in sctp_wake_up_waiters Daniel Borkmann
2014-04-08 23:32 ` Daniel Borkmann
2014-04-09 8:09 ` Daniel Borkmann
2014-04-09 8:09 ` Daniel Borkmann
2014-04-09 10:32 ` Daniel Borkmann
2014-04-09 10:32 ` Daniel Borkmann
2014-04-09 10:59 ` Neil Horman
2014-04-09 10:59 ` Neil Horman
2014-04-09 13:34 ` Daniel Borkmann [this message]
2014-04-09 13:34 ` Daniel Borkmann
2014-04-09 12:56 ` Vlad Yasevich
2014-04-09 12:56 ` Vlad Yasevich
2014-04-09 12:52 ` Vlad Yasevich
2014-04-09 12:52 ` Vlad Yasevich
2014-04-09 12:55 ` Vlad Yasevich
2014-04-09 12:55 ` Vlad Yasevich
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=53454C61.70007@redhat.com \
--to=dborkman@redhat.com \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=vyasevic@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 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.