Linux bluetooth development
 help / color / mirror / Atom feed
From: Jaganath <jaganath.k@samsung.com>
To: Andrei Emeltchenko <andrei.emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, s.syam@samsung.com
Subject: Re: [PATCH] Bluetooth: Free the l2cap channel list only when refcount is zero
Date: Fri, 13 Jul 2012 16:56:02 +0530	[thread overview]
Message-ID: <4368C8F191BB414F84A70D30771FE893@sisodomain.com> (raw)
In-Reply-To: <20120713084859.GC2729@aemeltch-MOBL1>

Hi Andrei,

--------------------------------------------------
From: "Andrei Emeltchenko" <andrei.emeltchenko.news@gmail.com>
Sent: Friday, July 13, 2012 2:19 PM
To: "Jaganath Kanakkassery" <jaganath.k@samsung.com>
Cc: <linux-bluetooth@vger.kernel.org>; <s.syam@samsung.com>
Subject: Re: [PATCH] Bluetooth: Free the l2cap channel list only when 
refcount is zero

> Hi Jaganath,
>
> On Fri, Jul 13, 2012 at 01:22:03PM +0530, Jaganath Kanakkassery wrote:
>> Move the l2cap channel list chan->global_l under the refcnt
>> protection and free it based on the refcnt.
>
> The idea is good.
>
>> Signed-off-by: Syam Sidhardhan <s.syam@samsung.com>
>> Signed-off-by: Jaganath Kanakkassery <jaganath.k@samsung.com>
>> ---
>>  include/net/bluetooth/l2cap.h |    5 +++--
>>  net/bluetooth/a2mp.c          |    2 +-
>>  net/bluetooth/l2cap_core.c    |    4 +++-
>>  net/bluetooth/l2cap_sock.c    |    2 +-
>>  4 files changed, 8 insertions(+), 5 deletions(-)
>>
>> diff --git a/include/net/bluetooth/l2cap.h 
>> b/include/net/bluetooth/l2cap.h
>> index e5164ff..4c0dcba 100644
>> --- a/include/net/bluetooth/l2cap.h
>> +++ b/include/net/bluetooth/l2cap.h
>> @@ -670,6 +670,8 @@ enum {
>>  L2CAP_EV_RECV_FRAME,
>>  };
>>
>> +void l2cap_chan_destroy(struct l2cap_chan *chan);
>> +
>
> What I think is that l2cap_chan_destroy shall be static if it is used only
> inside l2cap_chan_put. Then l2cap_chan_hold/put shall be moved to
> l2cap_core or l2cap_chan_destroy moved to header. First is better IMO.

Ok. We will split the patches into two.
1. Refactoring patch which moves l2cap_chan_put() and l2cap_chan_get()
to l2cap_core.c and the

2. Moving the l2cap channel list chan->global_l under the refcnt protection

>>  static inline void l2cap_chan_hold(struct l2cap_chan *c)
>>  {
>>  BT_DBG("chan %p orig refcnt %d", c, atomic_read(&c->refcnt));
>> @@ -682,7 +684,7 @@ static inline void l2cap_chan_put(struct l2cap_chan 
>> *c)
>>  BT_DBG("chan %p orig refcnt %d", c, atomic_read(&c->refcnt));
>>
>>  if (atomic_dec_and_test(&c->refcnt))
>> - kfree(c);
>> + l2cap_chan_destroy(c);
>
> It does make sense to use kref mechanism here.

Ok. Once this patch is done we will raise the kref patch.

> Best regards
> Andrei Emeltchenko

Thanks,
Jaganath

 


  reply	other threads:[~2012-07-13 11:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-13  7:52 [PATCH] Bluetooth: Free the l2cap channel list only when refcount is zero Jaganath Kanakkassery
2012-07-13  8:49 ` Andrei Emeltchenko
2012-07-13 11:26   ` Jaganath [this message]
2012-09-13 23:56     ` Maxim Levitsky
2012-09-14  9:45       ` Andrei Emeltchenko
2012-09-14 10:26         ` Maxim Levitsky

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=4368C8F191BB414F84A70D30771FE893@sisodomain.com \
    --to=jaganath.k@samsung.com \
    --cc=andrei.emeltchenko.news@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=s.syam@samsung.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