From: Jarek Poplawski <jarkao2@gmail.com>
To: Jay Cliburn <jacliburn@bellsouth.net>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Chris Snook <csnook@redhat.com>
Subject: Re: Need help debugging memory corruption
Date: Sun, 04 May 2008 16:55:08 +0200 [thread overview]
Message-ID: <481DCE4C.9070805@gmail.com> (raw)
In-Reply-To: <481DC731.5090303@gmail.com>
Jarek Poplawski wrote, On 05/04/2008 04:24 PM:
...
> I'm definitely with less experience, so I wonder why it can't be
> a simple race between atl1_clean_rx_ring() and something (maybe even
> pending atl1_intr_rx()) on the other cpu writing skb while kfreeing?
Hmm... atl1_intr_rx() looks impossible, so atl1_alloc_rx_buffers()?
Jarek P.
next prev parent reply other threads:[~2008-05-04 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 18:09 Need help debugging memory corruption Jay Cliburn
2008-05-04 14:24 ` Jarek Poplawski
2008-05-04 14:55 ` Jarek Poplawski [this message]
2008-05-04 19:55 ` Jay Cliburn
2008-05-05 7:27 ` Jarek Poplawski
2008-05-05 7:50 ` Jarek Poplawski
2008-05-04 15:02 ` Bart Van Assche
2008-05-04 19:52 ` Jay Cliburn
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=481DCE4C.9070805@gmail.com \
--to=jarkao2@gmail.com \
--cc=csnook@redhat.com \
--cc=jacliburn@bellsouth.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).