NetBSD Problem Report #54978

From ad@netbsd.org  Mon Feb 17 22:03:51 2020
Return-Path: <ad@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 67BEE1A9213
	for <gnats-bugs@gnats.NetBSD.org>; Mon, 17 Feb 2020 22:03:51 +0000 (UTC)
Message-Id: <20200217220351.2236384D55@mail.netbsd.org>
Date: Mon, 17 Feb 2020 22:03:51 +0000 (UTC)
From: ad@netbsd.org
Reply-To: ad@netbsd.org
To: gnats-bugs@NetBSD.org
Subject: cpu_need_proftick() can zap l_pflag
X-Send-Pr-Version: 3.95

>Number:         54978
>Category:       kern
>Synopsis:       cpu_need_proftick() can zap l_pflag
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    ad
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Feb 17 22:05:00 +0000 2020
>Last-Modified:  Mon Feb 17 22:29:47 +0000 2020
>Originator:     Andrew Doran
>Release:        NetBSD-current
>Organization:
	The NetBSD Project
>Environment:
NetBSD
Architecture: x86_64
Machine: amd64
>Description:
	cpu_need_proftick() looks like it ORs a value into curlwp->l_pflag
	from the context of statclock(), which it's assumed can fire @
	IPL_HIGH.  l_pflag is only for update by the LWP itself or when the
	LWP is known off the CPU.
>How-To-Repeat:
	Code inspection.
>Fix:
	Yes please.

>Release-Note:

>Audit-Trail:

Responsible-Changed-From-To: kern-bug-people->ad
Responsible-Changed-By: ad@NetBSD.org
Responsible-Changed-When: Mon, 17 Feb 2020 22:29:47 +0000
Responsible-Changed-Why:
take


>Unformatted:

Home	PR Database Search