All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland Tollenaar <rwatollenaar@domain.hid>
To: Wolfgang Grandegger <wg@domain.hid>
Cc: xenomai-help <xenomai@xenomai.org>, Jan Kiszka <jan.kiszka@domain.hid>
Subject: Re: [Xenomai-help] rtcan bufferoverflow but no evidence
Date: Tue, 14 Aug 2007 12:34:03 +0200	[thread overview]
Message-ID: <46C1851B.8040800@domain.hid> (raw)
In-Reply-To: <46C14FE2.8000507@domain.hid>

Hi,

> 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 
> -EAGAIN and the error mask shown there is weired as well.
> Roland, do you perform the open and close in a serialized way (same 
> task) and in nrt context?

I have now got the close loop with the printf in it. You are probably 
right that I was closing in the rt context because syslog shows an error 
from rtdm stating that one cannot close from rea time. I understand from 
a thread elsewhere that printf brings the program to secondary mode 
hence helps with the closing?

Its working now infallibly, no more open sockets remain so I can work 
like this. Also applied the suggestion to turn off the loopback with 
setsockopt and that functions well too (no more buffer overflows)

I only still have the problem with EML which does not seem happy in 
combination with rtcan. Even if I increase the rtskbf_cache_size value 
(now on 2048). It still occurs incidentally and even after the program 
has been running for a while. Anyhow that seems to have nothing to do 
with this topic....drifting a bit.


Thanks.

Roland


> 
> Wolfgang.
> 
> 
> 


      parent reply	other threads:[~2007-08-14 10:34 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
2007-08-14 10:34                   ` Roland Tollenaar [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=46C1851B.8040800@domain.hid \
    --to=rwatollenaar@domain.hid \
    --cc=jan.kiszka@domain.hid \
    --cc=rolandtollenaar@domain.hid \
    --cc=wg@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.