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: <20080502121945.GA18667@linuxace.com>
Date:	Fri, 2 May 2008 05:19:45 -0700
From:	Phil Oester <kernel@...uxace.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Ryan Roth <ryanroth@...global.net>, Ryan.Roth@...M.com,
	bugme-daemon@...zilla.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [Bugme-new] [Bug 10586] New: High Number of Segfaults onMacBookStarting With 2.6.24.5 Kernel

On Thu, May 01, 2008 at 07:28:38PM -0700, Andrew Morton wrote:
> On Thu, 1 May 2008 19:08:15 -0700 Phil Oester <kernel@...uxace.com> wrote:
> 
> > FWIW, I recently upgraded some boxes to 2.6.24.x, and started seeing tons of
> > qmail segfaults, which look remarkably similar to the above problem.  2.6.21
> > did not exhibit this issue.
> > 
> > May  1 22:06:03 mail80 kernel: qmail-smtpd[5319]: segfault at 0 ip 4884b473 sp fffeec1c error 4 in libc-2.6.so[487dd000+14e000]
> > May  1 22:06:03 mail80 kernel: qmail-smtpd[5491]: segfault at 0 ip 4884b473 sp ffb7179c error 4 in libc-2.6.so[487dd000+14e000]
> > May  1 22:06:03 mail80 kernel: qmail-smtpd[4669]: segfault at 0 ip 4884b473 sp fff3135c error 4 in libc-2.6.so[487dd000+14e000]
> > May  1 22:06:05 mail80 kernel: qmail-smtpd[5906]: segfault at 0 ip 4884b473 sp ffe1b24c error 4 in libc-2.6.so[487dd000+14e000]
> > May  1 22:06:07 mail80 kernel: qmail-smtpd[5898]: segfault at 0 ip 4884b473 sp ffe4e27c error 4 in libc-2.6.so[487dd000+14e000]
> > May  1 22:06:11 mail80 kernel: qmail-smtpd[5840]: segfault at 0 ip 4884b473 sp ffe04a2c error 4 in libc-2.6.so[487dd000+14e000]
> > 
> 
> Can you try fiddling with the norandmaps boot option and
> /proc/sys/kernel/randomize_va_space?

echo 0 > /proc/sys/kernel/randomize_va_space does not make any difference (and
is equivalent to norandmaps boot option according to docs).

Unless you have other ideas, I can try to bisect this later today.

Phil
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ