From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3F825C4338F for ; Mon, 9 Aug 2021 12:27:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1BA3B60F35 for ; Mon, 9 Aug 2021 12:27:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233826AbhHIM1e (ORCPT ); Mon, 9 Aug 2021 08:27:34 -0400 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:35583 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233698AbhHIM1e (ORCPT ); Mon, 9 Aug 2021 08:27:34 -0400 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 57E395C00DF; Mon, 9 Aug 2021 08:27:13 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Mon, 09 Aug 2021 08:27:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=AdJj11WOeMxOsGS2VukRYuSdN7K Cr738JS2MrX1t4AY=; b=O92RbYWvJ0NcMaHXf8NImaFUzVrVvFRqS6qxMbMH+Ag rx3ykbdvnAOIfPhbfQVriQD+OJbqC/eK6MujScW6OaS8jLjAp+XAIBMkcHMeaVJp xIimyBb6rOcpmPU+PRuZLaIeXU4OZZfIkJno9/acD1W3MmM9eSkbIpeKyHu5YDw5 ERN6zb/CBccfeOjeRSt74yrGujICz9HybnJPn+BmNQmbk12uNAw2rznQlhtnT7TH fSbPFD8q52C76UxgmHlwBXXqU3w9XrgOYseoNSjvlLQkKIYt7/imB9L/uKOoOCVe rcBhlebr6rTon9AeXEypanI07dgf4ArvVE34gAqbJYQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=AdJj11 WOeMxOsGS2VukRYuSdN7KCr738JS2MrX1t4AY=; b=U9itvKUmpzvSdzP2q9BB3w y6nBCu2Aua5QosJ38I+CkO2xnaQTW08dXaFMNvL/cKvPB89EFi6OAht3WLxY5OV1 y+dmrc1f+1bnhuUNeZP1ehbJ9ZBG0gBVn1JcesxCF6PMvscCKoY9ZD8g562h2oT+ P4UEcHfxmZ3zh3X6lGGCiylD8CxlqE3qrkBdui2ft5O0bfI8aK50Zze1beWnQsPL xAs+nRvF/1quZNWRfDqVnrx35R9KCS6UmCBT+DT7nSh/0w38RkdUXbXQg3707XmV IvfTHSaJO74hHpvknqBfsJtTg4HHwj/5s+C+erOOwaKm8jzX4h7+L0snIjxffOWw == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrjeejgdehfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkfhggtggujgesthdtredttddtvdenucfhrhhomhepifhrvghgucfm jfcuoehgrhgvgheskhhrohgrhhdrtghomheqnecuggftrfgrthhtvghrnhepveeuheejgf ffgfeivddukedvkedtleelleeghfeljeeiueeggeevueduudekvdetnecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepghhrvghgsehkrhhorghhrd gtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 9 Aug 2021 08:27:12 -0400 (EDT) Date: Mon, 9 Aug 2021 14:27:10 +0200 From: Greg KH To: nelakurthi koteswararao Cc: stable@vger.kernel.org, regressions@lists.linux.dev Subject: Re: Futex crash in Normal 4.9 Kernel Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Mon, Aug 09, 2021 at 05:52:17PM +0530, nelakurthi koteswararao wrote: > Dear Greg, > > Thank you for your reply. I noticed most of the futex changes between > 4.9.233 to 4.9.279 is related to Priority Inheritance that comes in > to use in the Real time kernel. But I am using the 4.9.232 Normal Kernel. I do not know what a "4.9.232 Normal Kernel" is. > That's the reason I posted futex crash to the mailing list for input. > is the race between futex_wait() thread and futex_wake() threads leading to > NULL pointer crash? any input in that direction? Again, please try the latest 4.9.y kernel release, we do not support older releases for obvious reasons. thanks, greg k-h