All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Andreas Glatz <andi.glatz@gmail.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] RTnet fixes - testers needed
Date: Tue, 19 Dec 2017 12:01:16 +0100	[thread overview]
Message-ID: <187aa958-ef0f-1691-bfb3-fed65b9f1b41@xenomai.org> (raw)
In-Reply-To: <CAKJ14NdXdqw5Y-UVp4vigRD5LF+-NCPmg+FzvrrNFd+tr9jWUg@mail.gmail.com>

On 12/19/2017 11:46 AM, Andreas Glatz wrote:
>>>>
>>>> I have pulled wip/rtnet-fixes branch with the last commit of Philippe from Sun
>>>> Dec 17 15:27:04 2017 +0100: net/udp: ioctl: fix temp arg buffer type
>>>>
>>>> I have created the packages and new kernel with the same configuration that I had.
>>>>
>>>> I run my application, that it's a POSIX application Wrapped and I still have the
>>>> same error when I activate SMAP:
>>>
>>> I see that the page fault occurs in rt_packet_ioctl()... by the looks
>>> of this bug it might be similar to the one I found in udp.c (see my
>>> post from Sunday)... basically the ioctl still tries to access user
>>> memory, which causes that stack trace. I'm currently a bit busy - I
>>> hope I can continue debugging this by the end of this week.
>>
>> I should be able to squeeze this debug task in the coming 48 hours, I
>> have your latest patched queued already. Let me know if you want to keep
>> on addressing this issue, otherwise I'll tackle this stuff.
>>
> 
> I think you'll be at it before me then :)

Not that sure, I'm discovering the rtnet implementation as I go actually.

 I already made some more
> progress in the UDP case. I can send you my latest patch tonight. I'm
> also happy to keep testing + fixing when I find time for it! I can use
> the RTnet UDP app from the company that I ported from kernel 3.0 to
> 4.9 to test the RTnet UDP stack.
> 

Thanks, let's progress on this front in parallel then: I'll let you keep
on fighting with the UDP stuff, and I'll dive into the AF_PACKET stuff.

Thanks,

-- 
Philippe.


  reply	other threads:[~2017-12-19 11:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 10:17 [Xenomai] RTnet fixes - testers needed Andreas Glatz
2017-12-19 10:38 ` Philippe Gerum
2017-12-19 10:46   ` Andreas Glatz
2017-12-19 11:01     ` Philippe Gerum [this message]
2017-12-20  9:00 ` Leopold Palomo-Avellaneda
2017-12-20  9:19   ` Andreas Glatz
2017-12-20 10:17 ` Philippe Gerum
2017-12-20 10:19   ` Philippe Gerum
2017-12-20 10:47     ` Philippe Gerum
2017-12-22 16:25       ` Leopold Palomo-Avellaneda
  -- strict thread matches above, loose matches on Subject: below --
2017-12-16 23:01 Andreas Glatz
2017-12-17 14:25 ` Philippe Gerum
2017-12-18  0:22   ` Andreas Glatz
2017-12-06 17:37 Philippe Gerum
2017-12-15 10:46 ` Leopold Palomo-Avellaneda
2017-12-15 11:04   ` Philippe Gerum
2017-12-15 12:25     ` Leopold Palomo-Avellaneda
2017-12-15 13:20       ` Jan Kiszka
2017-12-15 13:29         ` Philippe Gerum
2017-12-15 13:40           ` Jan Kiszka
2017-12-15 13:42             ` Leopold Palomo-Avellaneda
2017-12-15 13:48             ` Philippe Gerum
2017-12-15 20:42               ` Philippe Gerum
2017-12-18  6:33                 ` Jan Kiszka
2017-12-18 15:19                   ` Leopold Palomo-Avellaneda
2017-12-15 20:47       ` Philippe Gerum
2017-12-15 21:42         ` Leopold Palomo-Avellaneda

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=187aa958-ef0f-1691-bfb3-fed65b9f1b41@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=andi.glatz@gmail.com \
    --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.