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: <20080411013635.1F4B126F992@magilla.localdomain>
Date:	Thu, 10 Apr 2008 18:36:35 -0700 (PDT)
From:	Roland McGrath <roland@...hat.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Paul Mackerras <paulus@...ba.org>, linux-kernel@...r.kernel.org,
	linuxppc-dev@...abs.org
Subject: Re: [PATCH] powerpc TLF_RESTORE_SIGMASK

> This crashes my powerpc mac g5.

It worked fine on mine.

> It happens after the boot, during the first login-over-ssh.

Mine did lots of stuff fine.

> This is with most of the rest of the -mm poopile applied.  i386 and x86_64
> seem OK.

I had only tested with Linus's tree plus the small handful of post-2.6.25
cleanup patches I've posted in the last few weeks.  To be precise it was
9597362d354f8655ece324b01d0c640a0e99c077 plus several of my cleanup patches
(that are probably all in -mm, but I'm not sure off hand).

I'd rebased my tree today to 783e391b7b5b273cd20856d8f6f4878da8ec31b3
anyway.  I just tried the new kernel with the sigmask cleanups and only 
a few other patches, and have no problems.

The details of your crash make it look pretty unrelated to this code.
Off hand I would guess that it's some other bug from other -mm patches
that just happens only to bite you on powerpc.  If the crash is not
intermittent and you bisected it to this one change, then I am at a
loss to see what might be happening.  I'd have to leave it to Paul et
al to figure out if there is some strange powerpc juju going on.


Thanks,
Roland
--
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