From: Gustavo Padovan <padovan@profusion.mobi>
To: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCHv3 2/3] Bluetooth: Change sk lock to chan lock in L2CAP core
Date: Wed, 22 Feb 2012 16:41:46 -0200 [thread overview]
Message-ID: <20120222184146.GA23348@joana> (raw)
In-Reply-To: <1329923517-5425-3-git-send-email-Andrei.Emeltchenko.news@gmail.com>
Hi Andrei,
* Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com> [2012-02-22 17:11:56 +0200]:
> From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
>
> Change sk lock to chan lock in l2cap core and move sk locks
> to l2cap sock code. bh_locks were used because of being RCU
> critical section. When needed use explicit socket locks.
>
> Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> Reviewed-by: Ulisses Furquim <ulisses@profusion.mobi>
> ---
> net/bluetooth/l2cap_core.c | 166 ++++++++++++++++++++++++++------------------
> net/bluetooth/l2cap_sock.c | 18 ++++-
> 2 files changed, 114 insertions(+), 70 deletions(-)
Acked-by: Gustavo F. Padovan <padovan@profusion.mobi>
Now lets go to the next steps in the removal of socket usage inside L2CAP
core.
Gustavo
next prev parent reply other threads:[~2012-02-22 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 15:11 [PATCHv3 0/3] Bluetooth: Change socket lock to l2cap_chan lock Andrei Emeltchenko
2012-02-22 15:11 ` [PATCHv3 1/3] Bluetooth: Add unlocked __l2cap_chan_add function Andrei Emeltchenko
2012-02-22 15:11 ` [PATCHv3 2/3] Bluetooth: Change sk lock to chan lock in L2CAP core Andrei Emeltchenko
2012-02-22 18:41 ` Gustavo Padovan [this message]
2012-02-22 15:11 ` [PATCHv3 3/3] Bluetooth: Remove socket lock check Andrei Emeltchenko
2012-02-22 22:42 ` [PATCHv3 0/3] Bluetooth: Change socket lock to l2cap_chan lock Johan Hedberg
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=20120222184146.GA23348@joana \
--to=padovan@profusion.mobi \
--cc=Andrei.Emeltchenko.news@gmail.com \
--cc=linux-bluetooth@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).