Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp4654446imu; Tue, 29 Jan 2019 05:24:46 -0800 (PST) X-Google-Smtp-Source: ALg8bN7Px89JxeuxCap5F8U3d3fgwc+Op5m49m2+USg4BwhDzw1wSZ12awLkFPKoM6fP86iESPFh X-Received: by 2002:a17:902:8ec9:: with SMTP id x9mr26279845plo.27.1548768286670; Tue, 29 Jan 2019 05:24:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548768286; cv=none; d=google.com; s=arc-20160816; b=pZPJX73ONUFflHXMOPQTAUhWQ0lpaH368E7Kd9IciqNu+Kep/nf5HI0JZs53Yt14YF nZ0bKo5didVlrJRb4Xatokk4hgmzg5XkfvUu65Dms3wdvsXuBAwDORVviQb36vioV/0T U6GItVw6k+nnmzDYVirhIb5PaHCxiSAc7KfjsE8TWk1rOIiC0EESPMZgRrf5OvmAcXAK r9ggydpjNIR5CpOgbmkcv/Qr7x10AaKSIvSz++iZlfr9xHDFJLpTqwruq4YNXpm9DpSG NVhsazKPZRKJ/8+yRHbzE9RUfg9EwJD2N2HZZckfLhg5al3t7ywNu9K5ZCZbWKPJQf+0 7p9w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-disposition :content-transfer-encoding:message-id:in-reply-to:mime-version :references:subject:cc:to:from:date; bh=sZ+1dhn1iXsmauYrS5cbXPR/CawSWOO8ryVe8inqqDA=; b=REFtw5Vzofsri1/bTyVaQdtmX4DMWZz14P/clHkO5GTYoNmnU9ACC3iCvI5mpp5fb1 m85xsOM2CfbAt6t/Awb6BhjQdB5aVnm0nxy2/xphNFF1+xo6NRjKATBEcUKStPO7z8nX 3kCFnYFlPyBp86vgaBdQXcBsdaKpJrzuOhI5cuxQmpfNSk5jpTFwZ1mXwaWLLV1JGN/Q 7e4lcAeXMu01JVVACz417yfUSsIfvm6rFhuYfLJBPESpxECFNq3i6r9u5gLPu38aZl7K GqBjui4e93pv2mJJK0Z8ZwvKcTsHgG/Dfsqx5M0y9JZIHr8e7zXBR0hVWxT7KoziWtuE d6Kg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t65si781995pfd.246.2019.01.29.05.24.30; Tue, 29 Jan 2019 05:24:46 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727545AbfA2NXN (ORCPT + 99 others); Tue, 29 Jan 2019 08:23:13 -0500 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:39578 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725601AbfA2NXN (ORCPT ); Tue, 29 Jan 2019 08:23:13 -0500 Received: from pps.filterd (m0098420.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x0TDJpTt188282 for ; Tue, 29 Jan 2019 08:23:11 -0500 Received: from e06smtp02.uk.ibm.com (e06smtp02.uk.ibm.com [195.75.94.98]) by mx0b-001b2d01.pphosted.com with ESMTP id 2qaqhegh6w-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 29 Jan 2019 08:23:11 -0500 Received: from localhost by e06smtp02.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 29 Jan 2019 13:23:09 -0000 Received: from b06cxnps3074.portsmouth.uk.ibm.com (9.149.109.194) by e06smtp02.uk.ibm.com (192.168.101.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Tue, 29 Jan 2019 13:23:06 -0000 Received: from d06av24.portsmouth.uk.ibm.com (mk.ibm.com [9.149.105.60]) by b06cxnps3074.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x0TDN6SG16187564 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Tue, 29 Jan 2019 13:23:06 GMT Received: from d06av24.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 28DB04204F; Tue, 29 Jan 2019 13:23:05 +0000 (GMT) Received: from d06av24.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id DB0FE42049; Tue, 29 Jan 2019 13:23:04 +0000 (GMT) Received: from osiris (unknown [9.152.212.95]) by d06av24.portsmouth.uk.ibm.com (Postfix) with ESMTPS; Tue, 29 Jan 2019 13:23:04 +0000 (GMT) Date: Tue, 29 Jan 2019 14:23:03 +0100 From: Heiko Carstens To: Thomas Gleixner Cc: Peter Zijlstra , Ingo Molnar , Martin Schwidefsky , LKML , linux-s390@vger.kernel.org, Stefan Liebler , Sebastian Sewior Subject: Re: WARN_ON_ONCE(!new_owner) within wake_futex_pi() triggered References: <20181129112321.GB3449@osiris> <20190128134410.GA28485@hirez.programming.kicks-ass.net> <20190128135804.GB28878@hirez.programming.kicks-ass.net> <20190129090108.GA26906@osiris> <20190129102409.GB26906@osiris> <20190129103557.GF28485@hirez.programming.kicks-ass.net> MIME-Version: 1.0 In-Reply-To: X-TM-AS-GCONF: 00 x-cbid: 19012913-0008-0000-0000-000002B7763C X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19012913-0009-0000-0000-00002223B8F4 Message-Id: <20190129132303.GE26906@osiris> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Content-Disposition: inline X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-01-29_10:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=1 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1901290101 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 29, 2019 at 02:03:01PM +0100, Thomas Gleixner wrote: > On Tue, 29 Jan 2019, Peter Zijlstra wrote: > > > On Tue, Jan 29, 2019 at 11:24:09AM +0100, Heiko Carstens wrote: > > > > > Yes, sure. However ;) I reproduced the above with v5.0-rc4 + your > > > patch. And now I am trying to reproduce with linux-next 20190129 + > > > your patch and it doesn't trigger. Did I miss a patch which is only in > > > linux-next which could fix this? > > > > > > > I'm forever confused on what patch is where; but -ESRCH makes me thing > > maybe you lost this one: > > > > --- > > > > commit da791a667536bf8322042e38ca85d55a78d3c273 > > Author: Thomas Gleixner > > Date: Mon Dec 10 14:35:14 2018 +0100 > > That's in Linus tree already ... Yes, for some reason it's hardly reproducible now. It did hit once after an hour, but (of course) without tracing enabled... still trying.