From: David Miller <davem@davemloft.net>
To: alban.crequy@collabora.co.uk
Cc: eric.dumazet@gmail.com, lennart@poettering.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
ian.molton@collabora.co.uk
Subject: Re: [PATCH 5/8] af_unix: find the recipients of a multicast group
Date: Fri, 21 Jan 2011 16:58:39 -0800 (PST) [thread overview]
Message-ID: <20110121.165839.221575506.davem@davemloft.net> (raw)
In-Reply-To: <20110121172420.7ac74133@chocolatine.cbg.collabora.co.uk>
From: Alban Crequy <alban.crequy@collabora.co.uk>
Date: Fri, 21 Jan 2011 17:24:20 +0000
> I don't know if I should avoid releasing sockets in RCU callbacks or
> update the lockdep annotations.
Releasing sockets in RCU callbacks is dangerous at best.
next prev parent reply other threads:[~2011-01-22 0:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110121143751.57b1453d@chocolatine.cbg.collabora.co.uk>
2011-01-21 14:39 ` [PATCH 1/8] af_unix: Documentation on multicast unix sockets Alban Crequy
2011-01-21 14:39 ` [PATCH 2/8] af_unix: Add constant for unix socket options level Alban Crequy
2011-01-21 14:39 ` [PATCH 3/8] af_unix: add setsockopt on unix sockets Alban Crequy
2011-01-21 14:39 ` [PATCH 4/8] af_unix: create, join and leave multicast groups with setsockopt Alban Crequy
2011-01-21 14:39 ` [PATCH 5/8] af_unix: find the recipients of a multicast group Alban Crequy
2011-01-21 17:24 ` Alban Crequy
2011-01-22 0:58 ` David Miller [this message]
2011-01-21 14:39 ` [PATCH 6/8] af_unix: Deliver message to several recipients in case of multicast Alban Crequy
2011-01-21 14:39 ` [PATCH 7/8] af_unix: implement poll(POLLOUT) for multicast sockets Alban Crequy
2011-02-09 14:14 ` Alban Crequy
2011-01-21 14:39 ` [PATCH 8/8] af_unix: Unsubscribe sockets from their multicast groups on RCV_SHUTDOWN Alban Crequy
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=20110121.165839.221575506.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alban.crequy@collabora.co.uk \
--cc=eric.dumazet@gmail.com \
--cc=ian.molton@collabora.co.uk \
--cc=lennart@poettering.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).