From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Thu, 19 Jul 2012 14:40:38 +0300 From: Andrei Emeltchenko To: Jaganath Kanakkassery Cc: linux-bluetooth@vger.kernel.org, Johan Hedberg , Gustavo Padovan Subject: Re: [PATCH] Bluetooth: Fix socket not getting freed if l2cap channel create fails Message-ID: <20120719114037.GF26057@aemeltch-MOBL1> References: <1342682644-24964-1-git-send-email-jaganath.k@samsung.com> <20120719075239.GC26057@aemeltch-MOBL1> <760B2557394A4432BAFD74479AD7711B@sisodomain.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <760B2557394A4432BAFD74479AD7711B@sisodomain.com> Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Jaganath, On Thu, Jul 19, 2012 at 04:50:16PM +0530, Jaganath Kanakkassery wrote: > Hi Andrei, > > -------------------------------------------------- > From: "Andrei Emeltchenko" > Sent: Thursday, July 19, 2012 1:22 PM > To: "Jaganath Kanakkassery" > Cc: > Subject: Re: [PATCH] Bluetooth: Fix socket not getting freed if > l2cap channel create fails > > >Hi Jaganath, > > > >On Thu, Jul 19, 2012 at 12:54:04PM +0530, Jaganath Kanakkassery wrote: > >>If l2cap_chan_create() fails then it will return from l2cap_sock_kill > >>since zapped flag of sk is reset. > >> > >>Signed-off-by: Jaganath Kanakkassery > >>--- > >> net/bluetooth/l2cap_sock.c | 2 +- > >> 1 files changed, 1 insertions(+), 1 deletions(-) > >> > >>diff --git a/net/bluetooth/l2cap_sock.c b/net/bluetooth/l2cap_sock.c > >>index 79350d1..419857d 100644 > >>--- a/net/bluetooth/l2cap_sock.c > >>+++ b/net/bluetooth/l2cap_sock.c > >>@@ -1174,7 +1174,7 @@ static struct sock > >>*l2cap_sock_alloc(struct net *net, struct socket *sock, int p > >> > >> chan = l2cap_chan_create(); > >> if (!chan) { > >>- l2cap_sock_kill(sk); > >>+ sk_free(sk); > > > >Could you consider using sock_put which will call sk_free, > >maybe we need to add also sock_orphan? > > Ok, Actually I used sk_free since there is not refcount increase at > this point Have you tested it? It shall be 1, set by sock_init_data. > and also I found the same code in rfcomm_sock_alloc(). > So should I fix it in RFCOMM also? I think using sock_put would be the right approach. Maybe maintainers could comment here? Best regards Andrei Emeltchenko