netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: "Zhu, Yi" <yi.zhu@intel.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Sridhar Samudrala <sri@us.ibm.com>
Subject: Re: [PATCH V3 5/8] sctp: use limited socket backlog
Date: Fri, 05 Mar 2010 08:30:01 -0500	[thread overview]
Message-ID: <4B910759.6010505@hp.com> (raw)
In-Reply-To: <DA586906BA1FFC4384FCFD6429ECE860A4604767@shzsmsx502.ccr.corp.intel.com>



Zhu, Yi wrote:
> Eric Dumazet <eric.dumazet@gmail.com> wrote:
> 
>> As advertized by comment, we should hold the association *before*
>> accessing backlog queue.
> 
>> If order is not important, comment should be relaxed somehow ?
> 
> I don't see how the order is important here. We are under sock_lock 
> here thus nobody will race with us. IMHO, the comment talks about
> if a packet is queued into the backlog, we need to increase the assoc/ep
> reference count. Otherwise the assoc/ep might be disappeared when
> we are about to process it (by sctp_backlog_rcv) sometime later.
> 
> Thanks,
> -yi

Yes, that's correct.  The order is not really important since we
are under lock and are actually already holding a ref.  However
the ref will be dropped once we exit the function, so the function
takes an additional ref that is held while the packet is backloged.

You could get rid of the extra nesting though by returning early
if backlog failed.

-vlad

  parent reply	other threads:[~2010-03-05 13:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1267761707-15605-1-git-send-email-yi.zhu@intel.com>
2010-03-05  4:01 ` [PATCH V3 2/8] tcp: use limited socket backlog Zhu Yi
2010-03-05  4:01   ` [PATCH V3 3/8] udp: " Zhu Yi
2010-03-05  4:01     ` [PATCH V3 4/8] llc: " Zhu Yi
2010-03-05  4:01       ` [PATCH V3 5/8] sctp: " Zhu Yi
     [not found]         ` <1267761707-15605-6-git-send-email-yi.zhu@intel.com>
2010-03-05  4:01           ` [PATCH V3 7/8] x25: " Zhu Yi
2010-03-05  4:01             ` [PATCH V3 8/8] net: backlog functions rename Zhu Yi
2010-03-05  6:32               ` Eric Dumazet
2010-03-05 21:36                 ` David Miller
2010-03-05  6:30             ` [PATCH V3 7/8] x25: use limited socket backlog Eric Dumazet
2010-03-05  6:30           ` [PATCH V3 6/8] tipc: " Eric Dumazet
2010-03-05 20:48           ` Stephens, Allan
2010-03-05  6:28         ` [PATCH V3 5/8] sctp: " Eric Dumazet
2010-03-05 11:05           ` Zhu, Yi
2010-03-05 13:24             ` Eric Dumazet
2010-03-05 13:30             ` Vlad Yasevich [this message]
2010-03-05  6:22       ` [PATCH V3 4/8] llc: " Eric Dumazet
2010-03-05 13:00       ` Arnaldo Carvalho de Melo
2010-03-05  6:21     ` [PATCH V3 3/8] udp: " Eric Dumazet
2010-03-05  6:19   ` [PATCH V3 2/8] tcp: " Eric Dumazet
2010-03-08  9:21     ` Eric Dumazet
2010-03-08 18:46       ` David Miller
2010-03-05 13:00 ` [PATCH V3 1/8] net: add limit for " Arnaldo Carvalho de Melo

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=4B910759.6010505@hp.com \
    --to=vladislav.yasevich@hp.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=sri@us.ibm.com \
    --cc=yi.zhu@intel.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).