All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leopold Palomo-Avellaneda <leo@alaxarxa.net>
To: Philippe Gerum <rpm@xenomai.org>,
	"Xenomai@xenomai.org" <Xenomai@xenomai.org>
Subject: Re: [Xenomai] RTnet fixes - testers needed
Date: Fri, 15 Dec 2017 22:42:53 +0100	[thread overview]
Message-ID: <1d12f49c-6932-73e8-d29c-939a4f355eb8@alaxarxa.net> (raw)
In-Reply-To: <da516d20-d6fd-5043-8854-d648df01cf13@xenomai.org>

El 15/12/17 a les 21:47, Philippe Gerum ha escrit:
> On 12/15/2017 01:25 PM, Leopold Palomo-Avellaneda wrote:
>> Hi,
>>
>> I forgot something more:
>>
>> On 15/12/17 12:04, Philippe Gerum wrote:
>>
>> [...]
>>>>
>>>> I guess that there's something in the kernel config or somewhere in 3.x that
>>>> affects the PCI cards. In 2.6.x worked.
>>>
>>> On x86, I'd dare to say that it worked mostly by accident, as revealed
>>> by SMAP later on. RTnet was out of the Xenomai tree in 2.6.x, some
>>> changes introduced during the merge into 3.x might have caused
>>> regressions, or maybe some latent issues started to bite when transposed
>>> in a different environment, just like the SMAP problem on x86, revealing
>>> an ancient Rnet bug. I genuinely don't know when things started to hit
>>> the fan.
>>
>> I don't know if it's relevant or not, or I didn't understand it, but I think
>> that I still have problems with SMAP. If I activate it, I got:
>>
> 
> Please confirm that you are running wip/rtnet-fixes, and not
> stable-3.0.x or next which are still plagued with direct usermem access
> bugs. The backtrace shows SMAP biting in rt_packet_ioctl(), which is
> actually the first routine I fixed in the AF_PACKET layer, removing such
> invalid accesses, since I need that one.

well, I'm remotely connected to my robotic platform and it seems that it's the
version that I built on monday 3.0.6+ds2rtnet-1~drp9+20171211. I built it from:

xenomai-3.git (wip/rtnet-fixes)$

and these are the last two entries of the git:

commit c640a6040e72c7597d06b119d3ce30fbf3408e82
Author: Philippe Gerum <rpm@xenomai.org>
Date:   Wed Dec 6 13:41:06 2017 +0100

    net/iovec: drop useless kernel<-> iovec[] copy helpers

    No more in-tree users for those, in the wake of dropping the broken
    direct references from the kernel to user-space memory.

commit 64d2b7657ce4bddb2e2cc1a209dfedfa01000502
Author: Philippe Gerum <rpm@xenomai.org>
Date:   Wed Dec 6 13:40:19 2017 +0100

    net: convert to rtdm_get_iov_flatlen()


> If you still have this issue over the wip/rtnet-fixes branch, then
> please use addr2line to find out which source line triggers the bug in
> af_packet.c.

ok, on monday I will check again and I try to follow your indications.

Best regards,

Leopold



  reply	other threads:[~2017-12-15 21:42 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06 17:37 [Xenomai] RTnet fixes - testers needed 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 [this message]
2017-12-16 23:01 Andreas Glatz
2017-12-17 14:25 ` Philippe Gerum
2017-12-18  0:22   ` Andreas Glatz
2017-12-19 10:17 Andreas Glatz
2017-12-19 10:38 ` Philippe Gerum
2017-12-19 10:46   ` Andreas Glatz
2017-12-19 11:01     ` Philippe Gerum
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

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=1d12f49c-6932-73e8-d29c-939a4f355eb8@alaxarxa.net \
    --to=leo@alaxarxa.net \
    --cc=Xenomai@xenomai.org \
    --cc=rpm@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.