linux-kernel - Re: regression in 2.6.29-git3 on SH/Dreamcast

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] [day] [month] [year] [list]

Date:	Tue, 31 Mar 2009 08:32:33 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Manuel Lauss <mano@...rinelk.homelinux.net>
Cc:	Adrian McMenamin <adrian@...golddream.dyndns.info>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-sh <linux-sh@...r.kernel.org>
Subject: Re: regression in 2.6.29-git3 on SH/Dreamcast

On Mon, Mar 30, 2009 at 09:17:56AM +0200, Manuel Lauss wrote:
> Hi Adrian,
> 
> On Mon, Mar 30, 2009 at 12:35:58AM +0100, Adrian McMenamin wrote:
> > On Sun, 2009-03-29 at 20:04 +0100, Adrian McMenamin wrote:
> > > While 2.6.29 boots cleanly on the Dreamcast, later revisions are likely
> > > to crash with an OOM condition (this is a race, it doesn't happen on
> > > every boot, but on about one in every three or four).
> > > 
> > 
> > Still don't know why this timer patch is tipping the machine over, but I
> > have found that if I set CONFIG_NO_HZ=y then the machine will boot with
> > the patch applied.
> 
> I found that enabling swapfile support in Kconfig also reduces the frequency
> of OOMs on my sh7760.   While I don't experience your particular problem, my
> personal observation is that since around >2.6.22 linux-sh may OOM without
> actual swapspace a lot sooner  (i.e. post 2.6.25 I can't even do "emerge -pv
> world" without the kernel OOMing on me! This is with unreviewed platform code,
> so take this info with a mountain of salt).
> 
On a board with how much memory? What SLAB allocator are you using? This
is the first I have heard about any such issues, and if our memory
consumption drastically went up somewhere it would have been nice to know
when this became a problem. The Dreamcast is fixed at 16MB, and the
system in general is close to being OOM before it even makes it all the
way up. It would also be helpful to see the numbers with SLOB, which
should by the default on all of these systems.
--
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/