linux-kernel - Re: [Bugme-new] [Bug 10586] New: High Number of Segfaults onMacBookStarting With 2.6.24.5 Kernel

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]

Date:	Sat, 3 May 2008 08:59:09 -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 Fri, May 02, 2008 at 06:10:18AM -0700, Andrew Morton wrote:
> Traditionally i386 never printed that message (in fact neither architecture
> should - it allows poeple to spam the logs, but it is at least
> ratelimited).
> 
> In 2.6.23, i386 _does_ generate that message, in arch/i386/mm/fault.c
> 
> In 2.6.24 the i386 and x86_64 fault handlers were renamed to
> arch/x86/mm/fault_[32|64].c and both versions generated the message.
> 
> In 2.6.25 they were unified into a single arch/x86/mm/fault.c, and both
> architectures print the message.
> 
> So afacit 2.6.23 _should_ be printing the message if qmail is indeed
> generating a segfault.  But there's always the possibility that the
> message-printing code was simply broken in 2.6.23, and that your qmail has
> always been generating segfaults.

That is the most likely scenario.  I tried out 2.6.23, and it generates
the segfaults also.  And we're running a patched qmail-smtpd, so it likely
has been segfaulting "forever", but only became noticable in 2.6.23+.

Sorry for the noise.

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/