All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: rolandtollenaar@domain.hid
Cc: xenomai-help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] rtcan bufferoverflow but no evidence
Date: Tue, 14 Aug 2007 09:52:00 +0200	[thread overview]
Message-ID: <46C15F20.7070504@domain.hid> (raw)
In-Reply-To: <46C15CBA.8010804@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]

Roland Tollenaar wrote:
> Hi,
> 
>>> Recall that up to Xenomai 2.4 RTDM device/socket closing may fail (with
>>> -EAGAIN) when some other thread is currently using it and doesn't
>>> release it immediately when being "asked". That means for now you should
>>> loop over [rt_dev_]close as long as EAGAIN is returned.
>>
>> Roland, could you please check the return code of [rt_dev_]close.
>> Nevertheless, I'm still puzzled why the socket shows up in
>> /proc/rtcan/sockets because rtcan_raw_close() is called before returning 
> I have been battling with this all morning. I close with
> 
> do{
>     ret=rt_dev_close(can_fd);
>     //printf("%d",ret)
> while(ret!=-9)
> 
> but this only works (without fail) if I uncomment the printf line. I
> have now tried to put in a sleep(1) command instead but due to the crash
> caused  by commenting out hte crash (does not come out of loop) I am now
> trying to save my filesystem. :( :(.
> 

That really sounds like this issue, just applied on CAN:

http://sourceforge.net/mailarchive/forum.php?thread_name=9203.194.114.62.34.1186585293.squirrel%40webmail.krokoworld.de&forum_name=rtnet-users

If yes, you would have found a second reason to look at 2.4... ;)

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  reply	other threads:[~2007-08-14  7:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-13 14:58 [Xenomai-help] rtcan bufferoverflow but no evidence Roland Tollenaar
2007-08-13 15:38 ` Wolfgang Grandegger
     [not found]   ` <46C07D73.7070302@domain.hid>
     [not found]     ` <46C080C8.10906@domain.hid>
     [not found]       ` <46C0835E.8010105@domain.hid>
     [not found]         ` <46C0B036.3030306@domain.hid>
     [not found]           ` <46C0B1DF.6090509@domain.hid>
2007-08-13 19:59             ` Wolfgang Grandegger
2007-08-13 20:20               ` Roland Tollenaar
2007-08-13 20:07             ` Wolfgang Grandegger
2007-08-13 22:09               ` Jan Kiszka
2007-08-14  5:20                 ` Roland Tollenaar
2007-08-14  7:24                   ` Jan Kiszka
2007-08-14  6:46                 ` Wolfgang Grandegger
2007-08-14  7:41                   ` Roland Tollenaar
2007-08-14  7:52                     ` Jan Kiszka [this message]
2007-08-14 10:34                   ` Roland Tollenaar

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=46C15F20.7070504@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=rolandtollenaar@domain.hid \
    --cc=xenomai@xenomai.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.