From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 1 Dec 2010 19:16:35 -0200 From: "Gustavo F. Padovan" To: Andrei Emeltchenko Cc: Anderson Lizardo , linux-bluetooth@vger.kernel.org Subject: Re: [RFC 1/4] Bluetooth: clean up sco code Message-ID: <20101201211635.GD16125@vigoh> References: <1290784965-4508-1-git-send-email-Andrei.Emeltchenko.news@gmail.com> <1290784965-4508-2-git-send-email-Andrei.Emeltchenko.news@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 In-Reply-To: Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Andrei, * Andrei Emeltchenko [2010-12-01 15:44:50 +0200]: > Hi, > > On Fri, Nov 26, 2010 at 6:14 PM, Anderson Lizardo > wrote: > > Hi Andrei, > > > > On Fri, Nov 26, 2010 at 11:22 AM, Emeltchenko Andrei > > wrote: > >> @@ -828,13 +831,14 @@ static void sco_chan_del(struct sock *sk, int err) > >> > >>  static void sco_conn_ready(struct sco_conn *conn) > >>  { > >> -       struct sock *parent, *sk; > >> +       struct sock *parent; > >> +       struct sock *sk = conn->sk; > > > > I wonder if there is a problem with accessing conn->sk here outside > > the lock protection? > > I believe here is a safe access. We just acquire pointer and possible > protected operations > are executed inside lock. Agreed. -- Gustavo F. Padovan http://profusion.mobi