From owner-cvs-all  Sat Apr 20  9:23:55 2002
Delivered-To: cvs-all@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6FD8137B400; Sat, 20 Apr 2002 09:23:52 -0700 (PDT)
Received: (from jake@localhost)
	by freefall.freebsd.org (8.11.6/8.11.6) id g3KGNqe09261;
	Sat, 20 Apr 2002 09:23:52 -0700 (PDT)
	(envelope-from jake)
Message-Id: <200204201623.g3KGNqe09261@freefall.freebsd.org>
From: Jake Burkholder <jake@FreeBSD.org>
Date: Sat, 20 Apr 2002 09:23:52 -0700 (PDT)
To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: cvs commit: src/sys/sparc64/sparc64 rwindow.c
X-FreeBSD-CVS-Branch: HEAD
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
List-ID: <cvs-all.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20cvs-all>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20cvs-all>
X-Loop: FreeBSD.ORG

jake        2002/04/20 09:23:52 PDT

  Modified files:
    sys/sparc64/sparc64  rwindow.c 
  Log:
  Check the alignment of the stack pointer before copying in windows from the
  user stack in response to a failed window fill, allowing the process to be
  killed if its wrong.  This caused user programs which misalign their stack
  pointer to get stuck in an infinite loop at the kernel-userland boundary,
  which is mostly harmless.
  
  The same thing causes a fatal RED state exception on OpenBSD and probably
  NetBSD.
  
  Inspired by:    art@openbsd.org
  
  Revision  Changes    Path
  1.6       +4 -0      src/sys/sparc64/sparc64/rwindow.c

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message