From: Eric Dumazet <dada1@cosmosbay.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: netdev@vger.kernel.org
Subject: Re: What is lock_sock() before skb_free_datagram() for?
Date: Sat, 18 Apr 2009 10:09:57 +0200 [thread overview]
Message-ID: <49E98AD5.2010008@cosmosbay.com> (raw)
In-Reply-To: <200904181704.FDC21361.FQLOFHOOSVFtMJ@I-love.SAKURA.ne.jp>
Tetsuo Handa a écrit :
> Hello.
>
> udp_recvmsg() and udpv6_recvmsg() call skb_free_datagram() with
> lock_sock().
> But raw_recvmsg() and rawv6_recvmsg() call skb_free_datagram()
> without
> lock_sock().
> Is it OK?
Yes it is.
UDP protocol has memory accounting in recent kernels, not RAW.
next prev parent reply other threads:[~2009-04-18 8:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-18 8:04 What is lock_sock() before skb_free_datagram() for? Tetsuo Handa
2009-04-18 8:09 ` Eric Dumazet [this message]
2009-04-18 8:35 ` David Miller
2009-04-18 9:04 ` Tetsuo Handa
2009-04-18 9:08 ` David Miller
2009-04-18 12:23 ` Tetsuo Handa
2009-04-19 4:28 ` David Miller
2009-04-19 5:12 ` Tetsuo Handa
2009-04-19 7:44 ` David Miller
2009-04-23 14:57 ` Samir Bellabes
2009-04-23 21:56 ` Tetsuo Handa
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=49E98AD5.2010008@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=netdev@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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).