linux-kernel - Re: Need help debugging memory corruption

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080504145529.2eac672e@osprey.hogchain.net>
Date:	Sun, 4 May 2008 14:55:29 -0500
From:	Jay Cliburn <jacliburn@...lsouth.net>
To:	Jarek Poplawski <jarkao2@...il.com>
Cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	Chris Snook <csnook@...hat.com>
Subject: Re: Need help debugging memory corruption

On Sun, 04 May 2008 16:55:08 +0200
Jarek Poplawski <jarkao2@...il.com> wrote:

> 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()?

I booted with nosmp and the bug is *much* harder to hit, but I still
hit it once out of about 10 tries.  Does the fact that I hit it once
using nosmp disprove the race theory?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/