From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [RFC] android/hal-audio: Fix leaving open socket
Date: Tue, 10 Jun 2014 10:57:10 +0300 [thread overview]
Message-ID: <20140610075709.GA16337@aemeltch-MOBL1> (raw)
In-Reply-To: <CABBYNZK7tU6TL+M2beds0VPDU6T5AEv-5L8b=_q+r2Y1T_vAWw@mail.gmail.com>
Hi Luiz,
On Mon, Jun 09, 2014 at 04:31:13PM +0300, Luiz Augusto von Dentz wrote:
> Hi Andrei,
>
> On Thu, Jun 5, 2014 at 3:31 PM, Andrei Emeltchenko
> <Andrei.Emeltchenko.news@gmail.com> wrote:
> > From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> >
> > When getting out of the poll loop we shall close socket always.
> > ---
> > android/hal-audio.c | 12 +++++-------
> > 1 file changed, 5 insertions(+), 7 deletions(-)
> >
> > diff --git a/android/hal-audio.c b/android/hal-audio.c
> > index bfc102f..439b583 100644
> > --- a/android/hal-audio.c
> > +++ b/android/hal-audio.c
> > @@ -1346,14 +1346,12 @@ static void *ipc_handler(void *data)
> > /* Check if socket is still alive. Empty while loop.*/
> > while (poll(&pfd, 1, -1) < 0 && errno == EINTR);
> >
> > - if (pfd.revents & (POLLHUP | POLLERR | POLLNVAL)) {
> > - info("Audio HAL: Socket closed");
> > + info("Audio HAL: Socket closed");
> >
> > - pthread_mutex_lock(&sk_mutex);
> > - close(audio_sk);
> > - audio_sk = -1;
> > - pthread_mutex_unlock(&sk_mutex);
> > - }
> > + pthread_mutex_lock(&sk_mutex);
> > + close(audio_sk);
> > + audio_sk = -1;
> > + pthread_mutex_unlock(&sk_mutex);
> > }
> >
> > /* audio_sk is closed at this point, just cleanup endpoints states */
> > --
> > 1.8.3.2
>
> Im not quite sure what this does fix, I mean I do understand that the
> if statement might not be required after all we have since we have
> pfd.events = POLLHUP | POLLERR | POLLNVAL but removing it is not a fix
> more a cleanup.
Yes, it might be more cleanup. But the fact you check for EINTR implies
that there are other errors unchecked in which case we have resource leak.
Best regards
Andrei Emeltchenko
prev parent reply other threads:[~2014-06-10 7:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 12:31 [RFC] android/hal-audio: Fix leaving open socket Andrei Emeltchenko
2014-06-09 13:31 ` Luiz Augusto von Dentz
2014-06-10 7:57 ` Andrei Emeltchenko [this message]
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=20140610075709.GA16337@aemeltch-MOBL1 \
--to=andrei.emeltchenko.news@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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