From: Nicholas Mc Guire <der.herr@hofr.at>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Sami Pietik??inen <Sami.Pietikainen@wapice.com>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
Jouko Haapaluoma <jouko.haapaluoma@wapice.com>
Subject: Re: Crash in TCP/IP stack
Date: Sat, 25 Jan 2014 12:44:55 +0100 [thread overview]
Message-ID: <20140125114455.GA16350@opentech.at> (raw)
In-Reply-To: <20140124125639.GC10264@linutronix.de>
On Fri, 24 Jan 2014, Sebastian Andrzej Siewior wrote:
> * Sami Pietik??inen | 2013-12-17 10:21:33 [+0000]:
>
> >Hello,
> Hi Sami,
>
> >We have run into a crash in the TCP/IP stack when doing torture tests on our devices.
> >We have been able to reproduce this issue with Atmel SAMA5D35-EK using 3.6.9-rt21,
> >3.10.20-rt17 and 3.12.5-rt6 kernels and using Xilinx Zynq Zedboard with 3.8.13-rt15 kernel.
> >Unable to handle kernel NULL pointer dereference at virtual address 00000010
> >CPU: 0 PID: 7292 Comm: wget Not tainted 3.12.5-rt6-custom #1
> >[<c01989fc>] (__ip_make_skb+0x200/0x280) from [<c0198acf>] (ip_push_pending_frames+0xf/0x24)
> >[<c0198acf>] (ip_push_pending_frames+0xf/0x24) from [<c0198cf5>] (ip_send_unicast_reply+0x179/0x198)
> >[<c0198cf5>] (ip_send_unicast_reply+0x179/0x198) from [<c01a992d>] (tcp_v4_send_reset+0x10d/0x138)
> >[<c01a992d>] (tcp_v4_send_reset+0x10d/0x138) from [<c01aa491>] (tcp_v4_do_rcv+0x6d/0x168)
> >[<c01aa491>] (tcp_v4_do_rcv+0x6d/0x168) from [<c0175683>] (release_sock+0x63/0xe0)
> >[<c0175683>] (release_sock+0x63/0xe0) from [<c019f81b>] (tcp_close+0x12b/0x33c)
> >[<c019f81b>] (tcp_close+0x12b/0x33c) from [<c01b6b61>] (inet_release+0x25/0x44)
> >[<c01b6b61>] (inet_release+0x25/0x44) from [<c01731db>] (sock_release+0xf/0x5c)
> >[<c01731db>] (sock_release+0xf/0x5c) from [<c01733ed>] (sock_close+0x9/0xc)
> >[<c01733ed>] (sock_close+0x9/0xc) from [<c0065259>] (__fput+0x5d/0x17c)
> >[<c0065259>] (__fput+0x5d/0x17c) from [<c002469b>] (task_work_run+0x53/0x78)
> >[<c002469b>] (task_work_run+0x53/0x78) from [<c000e3ab>] (do_work_pending+0x5f/0x74)
> >[<c000e3ab>] (do_work_pending+0x5f/0x74) from [<c000cb53>] (work_pending+0x9/0x1a)
>
> Just that I have it tagged here properly. This bug seems to exist
> since v3.6-rt and Nicholas Mc Guire posted a fix for it.
>
yup - and the fix was confirmed to work atleast in the original setup
ref: http://www.spinics.net/lists/linux-rt-users/msg11081.html
ref: http://www.spinics.net/lists/linux-rt-users/msg11101.html
No test/confirmation for v3.6 though - if needed I can give it a spin
thx!
hofrat
next prev parent reply other threads:[~2014-01-25 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 10:21 Crash in TCP/IP stack Sami Pietikäinen
2014-01-24 12:56 ` Sebastian Andrzej Siewior
2014-01-25 11:44 ` Nicholas Mc Guire [this message]
2014-01-27 7:20 ` Sami Pietikäinen
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=20140125114455.GA16350@opentech.at \
--to=der.herr@hofr.at \
--cc=Sami.Pietikainen@wapice.com \
--cc=bigeasy@linutronix.de \
--cc=jouko.haapaluoma@wapice.com \
--cc=linux-rt-users@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox