From: Leopold Palomo-Avellaneda <leo@alaxarxa.net>
To: xenomai@xenomai.org
Subject: [Xenomai] rthal_strncpy_from_user bug
Date: Wed, 28 Sep 2016 13:12:12 +0200 [thread overview]
Message-ID: <52697293.XgM39KIdf6@soho> (raw)
Hi,
I'm trapped between 2.6.x and 3.x versions. The question to not boring you is
that I'm having a lot of problems with this soft 3.x so I try to go back again
to 2.6.
However, I need to use a modern hardware (new development) and 2.6 have some
issues especially rtnet that doesn't work without some patch with kernels
greater than 3.17 (or at least I'm not able to).
After solving some other issues my tests fails with some ugly message
(killed!!!!)
[ 5761.024502] RIP [<ffffffff8143079d>] rthal_strncpy_from_user+0xd/0x20
[ 5761.027017] RSP <ffff88045a493e20>
[ 5761.029456] CR2: 000000000040445d
[ 5761.031859] ---[ end trace f092b4db2a9a9654 ]---
[ 5773.810428] BUG: unable to handle kernel paging request at 000000000040445d
[ 5773.812909] IP: [<ffffffff8143079d>] rthal_strncpy_from_user+0xd/0x20
[ 5773.815389] PGD 45a00c067 PUD 456d4e067 PMD 45aa42067 PTE 4517f5025
[ 5773.817864] Oops: 0001 [#16] SMP
[ 5773.820293] Modules linked in: rt_igb(O) rt_e1000e(O) rt_loopback(O)
rtcfg(O) rtudp(O) rtipv4(O) rtmac(O) rtpacket(O) rtnet(O) ctr ccm binfmt_misc
nfsd auth_rpcgss nfs_acl nfs lockd fscache sunrpc nls_utf8 nls_cp437 vfat fat
xeno_can_peak_pci xeno_can_sja1000 xeno_can x86_pkg_temp_thermal coretemp
kvm_intel kvm peak_pci sja1000 joydev crc32_pclmul hid_generic usbhid
ghash_clmulni_intel aesni_intel ppdev aes_x86_64 lrw can_dev gf128mul
glue_helper xeno_rtdm snd_pcm snd_timer ablk_help
looking on the web, I have found that his issue was solved:
http://git.xenomai.org/xenomai-jki.git/commit/?h=maintenance-2.6&id=2eceef4c62bc8d6b3713787c26882fdcd9b87842
However, although it was on December 2015, 2.6.5 (July 2016) doesn't have it.
So, there's any reason why this patch was not pushed to 2.6.5?
Best regards,
Leopold
--
--
Linux User 152692 GPG: 05F4A7A949A2D9AA
Catalonia
-------------------------------------
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://xenomai.org/pipermail/xenomai/attachments/20160928/1f73e67e/attachment.sig>
next reply other threads:[~2016-09-28 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 11:12 Leopold Palomo-Avellaneda [this message]
2016-09-29 10:49 ` [Xenomai] rthal_strncpy_from_user bug Henning Schild
2016-09-29 11:04 ` Leopold Palomo-Avellaneda
2016-09-29 11:12 ` Leopold Palomo-Avellaneda
2018-12-22 8:34 ` C Smith
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=52697293.XgM39KIdf6@soho \
--to=leo@alaxarxa.net \
--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.