Linux bluetooth development
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: "Gustavo F. Padovan" <padovan@profusion.mobi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] avdtp: check if the socket is valid
Date: Thu, 20 Oct 2011 14:19:28 +0300	[thread overview]
Message-ID: <20111020111928.GA6486@fusion.localdomain> (raw)
In-Reply-To: <1318968186-6202-1-git-send-email-padovan@profusion.mobi>

Hi Gustavo,

On Tue, Oct 18, 2011, Gustavo F. Padovan wrote:
> ---
>  audio/avdtp.c |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/audio/avdtp.c b/audio/avdtp.c
> index d3568ba..08860d2 100644
> --- a/audio/avdtp.c
> +++ b/audio/avdtp.c
> @@ -523,6 +523,8 @@ static gboolean avdtp_send(struct avdtp *session, uint8_t transaction,
>  	}
>  
>  	sock = g_io_channel_unix_get_fd(session->io);
> +	if (!sock)
> +		return FALSE;
>  
>  	/* Single packet - no fragmentation */
>  	if (sizeof(struct avdtp_single_header) + len <= session->omtu) {

You'll need to give some more background when you're seeing this.
session->io should be set to NULL if we don't have a proper socket
available. Also, "if (!sock)" sounds like a weird check for a file
descriptor or socket where 0 is a valid value (typically reserved for
stdin but could get reused for something else in case a daemon-like
process has closed stdin, stdout and stderr). I.e. a validity check for
such a variable should be if (sock < 0), but as I said in this case you
should really investigate why session->io isn't NULL.

Johan

      reply	other threads:[~2011-10-20 11:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-18 20:03 [PATCH] avdtp: check if the socket is valid Gustavo F. Padovan
2011-10-20 11:19 ` Johan Hedberg [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=20111020111928.GA6486@fusion.localdomain \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=padovan@profusion.mobi \
    /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