Return-Path: Date: Fri, 29 Oct 2010 21:50:33 +0100 From: "Gustavo F. Padovan" To: Vinicius Gomes Cc: Ville Tervo , ext Anderson Briglia , "linux-bluetooth@vger.kernel.org" Subject: Re: [PATCH 2/6] Bluetooth: fix receiving L2CAP packets over LE Message-ID: <20101029205033.GB14961@vigoh> References: <1287791820-22693-3-git-send-email-anderson.briglia@openbossa.org> <20101029104435.GQ15050@null> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi, * Vinicius Gomes [2010-10-29 09:41:55 -0400]: > Hi Ville, > > On Fri, Oct 29, 2010 at 6:44 AM, Ville Tervo wrote: > > Hi Anderson, > > > > On Sat, Oct 23, 2010 at 01:56:56AM +0200, ext Anderson Briglia wrote: > >> From: Vinicius Costa Gomes > >> > >> As L2CAP packets coming over LE don't have any more encapsulation, > >> other than L2CAP, we are able to process them as soon as they arrive. > > > > Why is this change needed? Was something broken without this patch? > > > > This change is needed because without it the receiving side would > always think that it was receiving continuation frames. > > As the flags parameter is zero, it would fall into the "} else {" > condition, and because no frame was received before, conn->rx_len > would be zero and the frame would be discarded. Without this patch I > was seeing those "Unexpected continuation frame ..." messages on the > receiving side. >From what I understood the flags are only for ACL connections and LE links doesn't have fragmentation, right? So we don't need to check flags here, actually it seems we don't have flags for LE like ACL. -- Gustavo F. Padovan ProFUSION embedded systems - http://profusion.mobi