linux-kernel - Re: What to do with this message (2.6.30.1) ?

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20090715113740.334309dd.skraw@ithnet.com>
Date:	Wed, 15 Jul 2009 11:37:40 +0200
From:	Stephan von Krawczynski <skraw@...net.com>
To:	David Rientjes <rientjes@...gle.com>
Cc:	Jesse Brandeburg <jesse.brandeburg@...il.com>,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Justin Piszcz <jpiszcz@...idpixels.com>
Subject: Re: What to do with this message (2.6.30.1) ?

On Wed, 15 Jul 2009 01:18:02 -0700 (PDT)
David Rientjes <rientjes@...gle.com> wrote:

> On Wed, 15 Jul 2009, Stephan von Krawczynski wrote:
> [...]
> I added Justin Piszcz to the cc since he was having the same problem as 
> described in http://bugzilla.kernel.org/show_bug.cgi?id=13648.
> 
> He was unable to get slabtop -o output when this was happening, though, so 
> maybe you could grab a snapshot of that when you get these failures?  It 
> will help us figure out what cache the slab leak is in (assuming there is 
> one, >1G of slab on this machine is egregious).

I am pretty sure I can handle that. From the timestamps it looks like it
always happens when large amounts of data come in from rsyncs. These are
cronjobs, so I got the time.
Question: I just checked "slabtop -o" and found out it outputs exactly
nothing, whereas slabtop (without option -o) shows up just like (process) top
with lots of lines. Can you clarify why there is no console output at all with
option -o ? 

> Justin, were you using e1000e in your bug report?
> 
> If you have some additional time, it would also be helpful to get a 
> bisection of when the problem started occurring (it appears to be sometime 
> between 2.6.29 and 2.6.30).

Do you know what version should definitely be not affected? I can check one
kernel version per day, can you name a list which versions to check out? 

-- 
Regards,
Stephan
--
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/