From: David Miller <davem@davemloft.net>
To: dborkman@redhat.com
Cc: netdev@vger.kernel.org, nvbolhuis@aimvalley.nl
Subject: Re: [PATCH v3 net-next] packet: doc: describe PACKET_MMAP with one packet socket for rx and tx
Date: Fri, 10 Jan 2014 17:58:11 -0500 (EST) [thread overview]
Message-ID: <20140110.175811.1139439658496998152.davem@davemloft.net> (raw)
In-Reply-To: <1389345757-13579-1-git-send-email-dborkman@redhat.com>
From: Daniel Borkmann <dborkman@redhat.com>
Date: Fri, 10 Jan 2014 10:22:37 +0100
> From: Norbert van Bolhuis <nvbolhuis@aimvalley.nl>
>
> Document how to use one AF_PACKET mmap socket for RX and TX.
>
> Signed-off-by: Norbert van Bolhuis <nvbolhuis@aimvalley.nl>
> Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
Don't you need to evaluate need_rehook with at least the socket
lock held?
Otherwise how would two parallel bind() calls pan out?
prev parent reply other threads:[~2014-01-10 22:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 9:22 [PATCH v3 net-next] packet: doc: describe PACKET_MMAP with one packet socket for rx and tx Daniel Borkmann
2014-01-10 22:58 ` David Miller [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=20140110.175811.1139439658496998152.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nvbolhuis@aimvalley.nl \
/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