linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
	Nick Kossifidis <mickflemm@gmail.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	ath5k-devel@venema.h4ckr.net,
	"Luis R. Rodriguez" <lrodriguez@atheros.com>
Subject: Re: [TIP] BUG kmalloc-4096: Poison overwritten (ath5k_rx_skb_alloc)
Date: Sun, 28 Jun 2009 21:23:29 +0100	[thread overview]
Message-ID: <20090628202329.GB1546@sucs.org> (raw)
In-Reply-To: <20090526211029.GA2011@sucs.org>

On Tue, May 26, 2009 at 10:10:30PM +0100, Sitsofe Wheeler wrote:
> On Fri, May 22, 2009 at 10:39:31AM +0100, Sitsofe Wheeler wrote:
> > On Mon, May 18, 2009 at 11:05:40AM +0100, Sitsofe Wheeler wrote:
> > > On Fri, May 15, 2009 at 12:09:04AM -0400, Bob Copeland wrote:
> > > > 
> > > > This is too ugly to live, but I'd like to know if you can reproduce
> > > > with this patch.  If it still happens, then I guess it's back to
> > 
> > The poison message has not reappeared but this morning there was a
> 
> Yet again, I spoke too soon. This evening the following was in dmesg:
> 
> I'm pretty certain this kernel had your previous patch (although the
> directory that held the kernel has since been cleaned away on the server
> on which it was compiled).

OK I'm still trying to follow this. I forwarded your patch to 2.6.31-rc1
but this time I have kmemleak enabled. I left it streaming radio for the
past few hours and the following appeared in the logs:

Jun 28 17:01:34 eeepc kernel: [  744.083787] kmemleak: unreferenced object 0xf5845770 (size 64):
Jun 28 17:01:34 eeepc kernel: [  744.083795] kmemleak:   comm "swapper", pid 1, jiffies 4294673468
Jun 28 17:01:34 eeepc kernel: [  744.083799] kmemleak:   backtrace:
Jun 28 17:01:34 eeepc kernel: [  744.083811] kmemleak:     [<c01a749d>] kmemleak_alloc+0x11d/0x2a0
Jun 28 17:01:34 eeepc kernel: [  744.083818] kmemleak:     [<c01a4376>] __kmalloc+0x136/0x210
Jun 28 17:01:34 eeepc kernel: [  744.083828] kmemleak:     [<c043f923>] ieee80211_register_hw+0x83/0x4b0
Jun 28 17:01:34 eeepc kernel: [  744.083837] kmemleak:     [<c04630d5>] ath5k_pci_probe+0xee5/0x1100
Jun 28 17:01:34 eeepc kernel: [  744.083849] kmemleak:     [<c0279ab3>] local_pci_probe+0x13/0x20
Jun 28 17:01:34 eeepc kernel: [  744.083856] kmemleak:     [<c027a608>] pci_device_probe+0x68/0x90
Jun 28 17:01:34 eeepc kernel: [  744.083864] kmemleak:     [<c0312670>] driver_probe_device+0x70/0x140
Jun 28 17:01:34 eeepc kernel: [  744.083872] kmemleak:     [<c031293a>] __driver_attach+0x7a/0x80
Jun 28 17:01:34 eeepc kernel: [  744.083881] kmemleak:     [<c0311af9>] bus_for_each_dev+0x49/0x70
Jun 28 17:01:34 eeepc kernel: [  744.083888] kmemleak:     [<c031250e>] driver_attach+0x1e/0x20
Jun 28 17:01:34 eeepc kernel: [  744.083896] kmemleak:     [<c0312188>] bus_add_driver+0xd8/0x290
Jun 28 17:01:34 eeepc kernel: [  744.083904] kmemleak:     [<c0312a6f>] driver_register+0x5f/0x120
Jun 28 17:01:34 eeepc kernel: [  744.083911] kmemleak:     [<c027a443>] __pci_register_driver+0x53/0xc0
Jun 28 17:01:34 eeepc kernel: [  744.083922] kmemleak:     [<c061d82d>] init_ath5k_pci+0x1d/0x40
Jun 28 17:01:34 eeepc kernel: [  744.083929] kmemleak:     [<c0101122>] do_one_initcall+0x32/0x1d0
Jun 28 17:01:34 eeepc kernel: [  744.083939] kmemleak:     [<c05fe8aa>] kernel_init+0xba/0x110
Jun 28 17:01:34 eeepc kernel: [  744.084074] kmemleak: unreferenced object 0xf5845b60 (size 64):
Jun 28 17:01:34 eeepc kernel: [  744.084080] kmemleak:   comm "swapper", pid 1, jiffies 4294683694
Jun 28 17:01:34 eeepc kernel: [  744.084085] kmemleak:   backtrace:
Jun 28 17:01:34 eeepc kernel: [  744.084093] kmemleak:     [<c01a749d>] kmemleak_alloc+0x11d/0x2a0
Jun 28 17:01:34 eeepc kernel: [  744.084100] kmemleak:     [<c01a4376>] __kmalloc+0x136/0x210
Jun 28 17:01:34 eeepc kernel: [  744.084111] kmemleak:     [<c0239880>] __crypto_alloc_tfm+0x40/0x170
Jun 28 17:01:34 eeepc kernel: [  744.084120] kmemleak:     [<c0239cbc>] crypto_alloc_base+0x3c/0x80
Jun 28 17:01:34 eeepc kernel: [  744.084128] kmemleak:     [<c04420ff>] ieee80211_wep_init+0x2f/0x80
Jun 28 17:01:34 eeepc kernel: [  744.084136] kmemleak:     [<c043fa9d>] ieee80211_register_hw+0x1fd/0x4b0
Jun 28 17:01:34 eeepc kernel: [  744.084144] kmemleak:     [<c04630d5>] ath5k_pci_probe+0xee5/0x1100
Jun 28 17:01:34 eeepc kernel: [  744.084153] kmemleak:     [<c0279ab3>] local_pci_probe+0x13/0x20
Jun 28 17:01:34 eeepc kernel: [  744.084160] kmemleak:     [<c027a608>] pci_device_probe+0x68/0x90
Jun 28 17:01:34 eeepc kernel: [  744.084168] kmemleak:     [<c0312670>] driver_probe_device+0x70/0x140
Jun 28 17:01:34 eeepc kernel: [  744.084175] kmemleak:     [<c031293a>] __driver_attach+0x7a/0x80
Jun 28 17:01:34 eeepc kernel: [  744.084184] kmemleak:     [<c0311af9>] bus_for_each_dev+0x49/0x70
Jun 28 17:01:34 eeepc kernel: [  744.084191] kmemleak:     [<c031250e>] driver_attach+0x1e/0x20
Jun 28 17:01:34 eeepc kernel: [  744.084199] kmemleak:     [<c0312188>] bus_add_driver+0xd8/0x290
Jun 28 17:01:34 eeepc kernel: [  744.084207] kmemleak:     [<c0312a6f>] driver_register+0x5f/0x120
Jun 28 17:01:34 eeepc kernel: [  744.084214] kmemleak:     [<c027a443>] __pci_register_driver+0x53/0xc0

There were quite a few leaks before this. I dunno if kmemleak is
spurious or not. As always, any ideas?

-- 
Sitsofe | http://sucs.org/~sits/

  reply	other threads:[~2009-06-28 20:23 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-22 11:18 [TIP] BUG kmalloc-4096: Poison overwritten (ath5k_rx_skb_alloc) Sitsofe Wheeler
2009-02-22 12:01 ` Jiri Slaby
2009-02-22 12:20   ` Sitsofe Wheeler
2009-02-22 12:47     ` Jiri Slaby
2009-02-22 14:47     ` Frederic Weisbecker
2009-02-22 17:02       ` Sitsofe Wheeler
2009-02-22 17:10         ` Frederic Weisbecker
2009-02-22 19:27           ` Jiri Slaby
2009-02-22 19:42             ` Frederic Weisbecker
2009-02-22 20:18               ` Sitsofe Wheeler
2009-02-22 20:27                 ` Jiri Slaby
2009-02-22 20:30                 ` Frederic Weisbecker
2009-02-22 21:56         ` Jiri Slaby
2009-02-22 22:21           ` Sitsofe Wheeler
2009-02-22 23:20           ` Jiri Slaby
2009-02-23 15:35             ` Bob Copeland
2009-02-23 16:03               ` Nick Kossifidis
2009-02-23 16:15                 ` Nick Kossifidis
2009-02-23 16:21                   ` Bob Copeland
2009-02-23 16:27                     ` Nick Kossifidis
2009-02-23 16:30                       ` Bob Copeland
2009-02-23 16:41                         ` Nick Kossifidis
2009-02-23 16:44                           ` Bob Copeland
2009-02-23 16:16                 ` pat-lkml
2009-02-23 16:20                   ` Nick Kossifidis
2009-02-23 22:22               ` Jiri Slaby
2009-02-23 22:43                 ` Jiri Slaby
2009-02-23 23:08                   ` Nick Kossifidis
2009-02-24 13:58                     ` Bob Copeland
2009-02-24 21:47                       ` Jiri Slaby
2009-02-25 14:01                         ` Sitsofe Wheeler
2009-02-26  1:06                           ` Bob Copeland
2009-02-26 20:53                             ` Jiri Slaby
2009-02-26 21:05                               ` Bob Copeland
2009-02-26 13:59                           ` Bob Copeland
2009-02-26 17:03                             ` Sitsofe Wheeler
2009-03-02 17:34                               ` [ath5k-devel] " Bob Copeland
2009-03-03  4:12                               ` Bob Copeland
2009-03-03 20:03                                 ` Sitsofe Wheeler
2009-03-04 12:07                                   ` Bob Copeland
2009-03-06  9:42                                     ` Sitsofe Wheeler
2009-03-07  4:47                                       ` Bob Copeland
2009-03-07  8:04                                         ` Sitsofe Wheeler
2009-03-07 13:34                                           ` Bob Copeland
2009-03-08  3:09                                       ` Bob Copeland
2009-03-08  9:28                                         ` Jiri Slaby
2009-03-08 16:10                                           ` Bob Copeland
2009-03-10  0:43                                           ` Bob Copeland
2009-03-10  8:19                                             ` Sitsofe Wheeler
2009-03-12  6:10                                             ` Sitsofe Wheeler
2009-03-13  9:52                                               ` Sitsofe Wheeler
2009-03-13 12:28                                                 ` Bob Copeland
2009-03-20 13:14                                                 ` Bob Copeland
2009-03-29 14:24                                                   ` Sitsofe Wheeler
2009-03-29 15:14                                                     ` Bob Copeland
2009-03-31  8:30                                                       ` Sitsofe Wheeler
2009-05-13 21:44                                                         ` Sitsofe Wheeler
2009-05-15  4:09                                                           ` Bob Copeland
2009-05-18 10:05                                                             ` Sitsofe Wheeler
2009-05-22  9:39                                                               ` Sitsofe Wheeler
2009-05-22 12:06                                                                 ` Bob Copeland
2009-05-26 21:10                                                                 ` Sitsofe Wheeler
2009-06-28 20:23                                                                   ` Sitsofe Wheeler [this message]
2009-07-14  2:24                                                                     ` Bob Copeland
2009-02-26  1:11                         ` Bob Copeland
2009-02-22 20:17       ` Bob Copeland

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=20090628202329.GB1546@sucs.org \
    --to=sitsofe@yahoo.com \
    --cc=ath5k-devel@venema.h4ckr.net \
    --cc=fweisbec@gmail.com \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lrodriguez@atheros.com \
    --cc=me@bobcopeland.com \
    --cc=mickflemm@gmail.com \
    /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).