public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Jose Vasconcellos <jose@vasmac.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] socket connect returns EAGAIN
Date: Wed, 13 Sep 2006 10:21:54 -0400	[thread overview]
Message-ID: <45081402.8020909@vasmac.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0609121206040.17868@redbean.intranet.gw-instruments.de>

Peter Wippich wrote:
> Hi Marcel, 
>
> On Tue, 12 Sep 2006, Marcel Holtmann wrote:
>
>   
>> Hi Peter,
>>
>>     
>>> see my last post on this subject about 4 days ago. From my understanding 
>>> they shall return EINPROGRESS when the connection to the remote device is 
>>> pending. Returning EAGAIN looks like a small bug. See also man 2 connect 
>>> or man 7 socket. 
>>>       
>> this has been raised a long time ago. However the Bluetooth core inside
>> the kernel doesn't sets the wrong error. It is one of the network
>> functions we use.
>>     
>
> Are you sure ?!? 
>
> I think the problem is in bt_sock_wait_state(...). This always returns 
> -EAGAIN if timeout is zero (which it is if the socket is set non 
> blocking). But may be I'm missing something. 
>
> Ciao, 
>
> Peter 
>
>   
Hi Peter,

I've come to a similar conclusion. I'm not sure why it's returning -EAGAIN.
However, looking at the x25 transport (af_x25.c), it takes a different 
approach;
if O_NONBLOCK is set they don't call the blocking routine at all. Maybe a
similar approach should be taken here.

Jose


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2006-09-13 14:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-12  0:47 [Bluez-devel] socket connect returns EAGAIN Jose Vasconcellos
2006-09-12  8:40 ` Peter Wippich
2006-09-12  8:43   ` Marcel Holtmann
2006-09-12 10:13     ` Peter Wippich
2006-09-12 10:29       ` Marcel Holtmann
2006-09-13 14:21       ` Jose Vasconcellos [this message]
2006-09-14  9:01         ` Peter Wippich
2006-09-15  9:49           ` Marcel Holtmann
2006-09-20 14:48             ` Ulisses Furquim
2006-09-20 15:00               ` Peter Wippich
2006-09-20 15:05               ` Marcel Holtmann
2006-09-21 19:59                 ` Ulisses Furquim
2006-09-21 20:05                   ` Marcel Holtmann
2006-09-22 17:47                     ` Ulisses Furquim

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=45081402.8020909@vasmac.com \
    --to=jose@vasmac.com \
    --cc=bluez-devel@lists.sourceforge.net \
    /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