From: Gustavo Zacarias <gustavoz@gentoo.org>
To: sparclinux@vger.kernel.org
Subject: Re: [Systems] Re: Oops in tcp_sendmsg on T[12]000
Date: Mon, 19 Mar 2007 16:40:36 +0000 [thread overview]
Message-ID: <45FEBD04.9060907@gentoo.org> (raw)
In-Reply-To: <1818c1980703052246p5af31178p70296e156b06511a@mail.gmail.com>
David Miller wrote:
> Ok, I think the following patch is the bug fix. I'm running a bunch
> of further stress testing to make sure this is indeed the cause of
> these crashes.
>
> Let me know if you can still trigger the bug with this patch
> applied, thanks!
>
> Assuming all goes well I'll push this upstream to Linus and
> also to the -stable 2.6.x branches.
>
> [SPARC64]: store-init needs trailing membar.
>
> The manual says that it is required and we actually have crash reports
> where loads see stale data due to not having membars here.
>
> In one case the networking does:
>
> memset(skb, 0, offsetof(struct sk_buff, truesize));
>
> and then some code later checks skb->nohdr for zero, but it's still
> the value that was there before the memset().
Been running some intensive network loads on our T2000 for the last
couple of hours and indeed this patch seems to fix it. Previously it
would trigger an oops in less than 10 minutes.
Thanks.
--
Gustavo Zacarias
Gentoo/SPARC monkey
next prev parent reply other threads:[~2007-03-19 16:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 6:46 [Systems] Re: Oops in tcp_sendmsg on T[12]000 Corey Shields
2007-03-06 15:22 ` Jason Wever
2007-03-12 23:58 ` Narayan Newton
2007-03-13 2:50 ` David Miller
2007-03-17 20:23 ` David Miller
2007-03-19 7:41 ` David Miller
2007-03-19 16:40 ` Gustavo Zacarias [this message]
2007-03-19 18:58 ` David Miller
2007-03-20 20:41 ` Narayan Newton
2007-03-20 22:47 ` David Miller
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=45FEBD04.9060907@gentoo.org \
--to=gustavoz@gentoo.org \
--cc=sparclinux@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 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.