mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Laurent Chavey <chavey@google.com>
To: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Cc: Roger Oksanen <roger.oksanen@cs.helsinki.fi>,
	Alan Stern <stern@rowland.harvard.edu>,
	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
	"Allan, Bruce W" <bruce.w.allan@intel.com>,
	"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>,
	"Ronciak, John" <john.ronciak@intel.com>,
	"e1000-devel@lists.sourceforge.net" 
	<e1000-devel@lists.sourceforge.net>,
	Kernel development list <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	David Miller <davem@davemloft.net>
Subject: Re: e100 REGRESSION in 2.6.32 (PATCH v2)
Date: Thu, 17 Dec 2009 13:15:04 -0800	[thread overview]
Message-ID: <97949e3e0912171315g537903f7m9461ea8399dc018c@mail.gmail.com> (raw)
In-Reply-To: <alpine.WNT.2.00.0912170919010.2612@jbrandeb-desk1.amr.corp.intel.com>

when using DMAPOOL_DEBUG, do we really want to
over-write 	memset(retval, POOL_POISON_ALLOCATED, pool->size);
set in  dma_pool_alloc.


On Thu, Dec 17, 2009 at 9:21 AM, Brandeburg, Jesse
<jesse.brandeburg@intel.com> wrote:
>
> On Thu, 17 Dec 2009, Roger Oksanen wrote:
>> e100: Fix broken cbs accounting due to missing memset.
>>
>> Alan Stern noticed that e100 caused slab corruption.
>> commit 98468efddb101f8a29af974101c17ba513b07be1 changed
>> the allocation of cbs to use dma pools that don't return zeroed memory,
>> especially the cb->status field used to track which cb to clean, causing
>> (the visible) double freeing of skbs and a wrong free cbs count.
>>
>> Now the cbs are explicitly zeroed at allocation time.
>>
>> Reported-by: Alan Stern <stern@rowland.harvard.edu>
>> Tested-by: Alan Stern <stern@rowland.harvard.edu>
>> Signed-off-by: Roger Oksanen <roger.oksanen@cs.helsinki.fi>
>
> Change looks reasonable, ACK.
>
> should we also consider a followon patch to zero memory allocated with
> pci_pools?  Seems useful.
>
> Acked-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2009-12-17 21:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15 22:17 e100 REGRESSION in 2.6.32 Alan Stern
2009-12-16 18:21 ` Brandeburg, Jesse
2009-12-16 19:11   ` David Miller
2009-12-16 19:50   ` Alan Stern
2009-12-16 20:46     ` Roger Oksanen
2009-12-17 12:14     ` e100 REGRESSION in 2.6.32 (PATCH) Roger Oksanen
2009-12-17 15:47       ` Alan Stern
2009-12-17 16:10         ` e100 REGRESSION in 2.6.32 (PATCH v2) Roger Oksanen
2009-12-17 17:21           ` Brandeburg, Jesse
2009-12-17 21:15             ` Laurent Chavey [this message]
2009-12-19  4:19             ` 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=97949e3e0912171315g537903f7m9461ea8399dc018c@mail.gmail.com \
    --to=chavey@google.com \
    --cc=bruce.w.allan@intel.com \
    --cc=davem@davemloft.net \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=john.ronciak@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=peter.p.waskiewicz.jr@intel.com \
    --cc=roger.oksanen@cs.helsinki.fi \
    --cc=stern@rowland.harvard.edu \
    /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

all inboxes | Powered by JetHome®