Received: by 2002:a05:6358:bb9e:b0:b9:5105:a5b4 with SMTP id df30csp699249rwb; Sat, 3 Sep 2022 00:35:36 -0700 (PDT) X-Google-Smtp-Source: AA6agR49+jreYsRiUExE1xOgGHf3j9uDOS+95ocoXMse3E8K1ATzLzXej2iJOpYYwkQ2QX5wLxdj X-Received: by 2002:a17:90b:3504:b0:1fe:49ba:b71a with SMTP id ls4-20020a17090b350400b001fe49bab71amr8533559pjb.99.1662190536180; Sat, 03 Sep 2022 00:35:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1662190536; cv=none; d=google.com; s=arc-20160816; b=IWuRAQ/tNwW9s4RgcynGG7NnTDdLgMPsnlZZc4avtjd+kp3sFCg1e+U28cdRb4dJnT iLBYHIW3jsziK/5wba37fsGe6RlDoal2bude782+8JoKLlWYS8A4mC7qrZCiSpghzI8G r3YMbkh2Fm0m4g5jEtdg6eaMskgLMv0Eu7rwyTdPyp4aHEoOMUat74dtWJZbABs64KWJ SE/EQpEGjt1HTJmTgHb0hHSZw6PFGZ4chAkyuE11GOQteSDF6o3lfTjRgbZOG4HKCapT kwPMBjxnkEPumVpPrsz65FgXTysh6r/5ZCyHvy+DpO2TSuSSuDZaTqpgOa5tSuP402R0 qn4g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=UHFFj9vepk7u9EoGJKlFbytlhoGP7nwiP3Wn6nevpP8=; b=w+SzTIiBKTRLetyX93lVkIEJgsnEOmvawWmkQ/CHXh0gr5xNPgO2MTmnZ4X+sZ+9vY ZNjad5TNG1EPb59KhjJythXSCtixSndQYQVAxP37hWe66J7EJS3JjuV+hpq/ZZYIP8OX MIQR5jkOS1fL3Hky7sMemR3D5sJsMEWyprmrYhahkcddzrpasY48ZqCpr3gAaQYcHOS5 I3n5L6m3ngD39p3bIFygQhu0Edu0Ox0hZ5zDzGEVtZU4rRxwUNPCL+j3iyVYt5kUU8AC iG+bKI9sF6NUBxLZ1Yt5fiIJeXdaBtbibtXYOMQbNlf061CbKgjTjd3rRntOdsBPnwrP ze3Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=JMGvW7VR; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id q6-20020a63cc46000000b0042b1451d39asi2764977pgi.37.2022.09.03.00.35.24; Sat, 03 Sep 2022 00:35:36 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=JMGvW7VR; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233037AbiICHUh (ORCPT + 99 others); Sat, 3 Sep 2022 03:20:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50856 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233006AbiICHUe (ORCPT ); Sat, 3 Sep 2022 03:20:34 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2D05B6DF95 for ; Sat, 3 Sep 2022 00:20:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1662189632; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=UHFFj9vepk7u9EoGJKlFbytlhoGP7nwiP3Wn6nevpP8=; b=JMGvW7VRGtqlEeEC8VsqYq+75zWvq7TvFqYH9RljL0bBISbKQBYQDHSXdsi0II1G8F3/gq r/Vc1+ig8WNLmFsY7/tZRVRJ7uSnIhCg7q4pCCL+fMr9OXFAaK3Q1iThjO5XWufElsVJQv GKqtOEH/canBWa0tCi6ZbplgM4NqPio= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-465-ppu4bCiwMhe62PT5SwKPug-1; Sat, 03 Sep 2022 03:20:28 -0400 X-MC-Unique: ppu4bCiwMhe62PT5SwKPug-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 3BED7811E76; Sat, 3 Sep 2022 07:20:27 +0000 (UTC) Received: from dhcp-27-174.brq.redhat.com (unknown [10.40.192.34]) by smtp.corp.redhat.com (Postfix) with SMTP id 33575422E3; Sat, 3 Sep 2022 07:20:20 +0000 (UTC) Received: by dhcp-27-174.brq.redhat.com (nbSMTP-1.00) for uid 1000 oleg@redhat.com; Sat, 3 Sep 2022 09:20:26 +0200 (CEST) Date: Sat, 3 Sep 2022 09:20:19 +0200 From: Oleg Nesterov To: Oleksandr Natalenko Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org, Jonathan Corbet , Alexander Viro , Andrew Morton , Huang Ying , "Jason A . Donenfeld" , Will Deacon , "Guilherme G . Piccoli" , Laurent Dufour , Stephen Kitt , Rob Herring , Joel Savitz , "Eric W . Biederman" , Kees Cook , Xiaoming Ni , Luis Chamberlain , Renaud =?iso-8859-1?Q?M=E9trich?= , Grzegorz Halat , Qi Guo Subject: Re: [PATCH] core_pattern: add CPU specifier Message-ID: <20220903072018.GA15331@redhat.com> References: <20220903064330.20772-1-oleksandr@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220903064330.20772-1-oleksandr@redhat.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-Scanned-By: MIMEDefang 2.79 on 10.11.54.5 X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/03, Oleksandr Natalenko wrote: > > Statistically, in a large deployment regular segfaults may indicate a CPU issue. > > Currently, it is not possible to find out what CPU the segfault happened on. > There are at least two attempts to improve segfault logging with this regard, > but they do not help in case the logs rotate. > > Hence, lets make sure it is possible to permanently record a CPU > the task ran on using a new core_pattern specifier. > > Suggested-by: Renaud M?trich > Signed-off-by: Oleksandr Natalenko > --- > Documentation/admin-guide/sysctl/kernel.rst | 1 + > fs/coredump.c | 5 +++++ > include/linux/coredump.h | 1 + > 3 files changed, 7 insertions(+) Reviewed-by: Oleg Nesterov