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=-7.0 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=unavailable 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 BFF2EC06511 for ; Tue, 2 Jul 2019 08:12:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 90A89206A2 for ; Tue, 2 Jul 2019 08:12:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1562055135; bh=RSOkxXSyZ2sNkeOzn5fr775UMm1wxH2xyAEoEIewI0U=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=kGTG2bAN+Inr0z+B5MSf/ZArCJLEQLRPy2gg4MU/mHV65rKGMtCt1m/y6fNGu+erI yUBnSB4w3cLjzVkiufmvE2euPa+FJt4SkOhG2+WvGSo+7C2Upb40g7fHe2orrJCLS9 mBzXL3yY4cE9TfqT7y2RxGfHcpp6D1HzJqN/4g+s= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728604AbfGBIJK (ORCPT ); Tue, 2 Jul 2019 04:09:10 -0400 Received: from mail.kernel.org ([198.145.29.99]:56924 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728584AbfGBIJJ (ORCPT ); Tue, 2 Jul 2019 04:09:09 -0400 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 85FED20665; Tue, 2 Jul 2019 08:09:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1562054949; bh=RSOkxXSyZ2sNkeOzn5fr775UMm1wxH2xyAEoEIewI0U=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=deJNS07DoWhq6sucpkLontge4OBuzXB+8rBfr+C2lUsTl+omgdBKb/zbgkygpU3pA sfbGBdr/iJRTUVrLWtikydTRPPfNMgxPtRJlQ8F0lHiF/hxXYL+567uhGf9wDw8mje VFk/EwlxFNFgKfHX4BKDMPIJf3gKTN9D8sxzZBVU= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, John Ogness , Jan Luebbe , Alexey Dobriyan , Andy Lutomirski , Andrew Morton , Linus Torvalds Subject: [PATCH 4.14 16/43] fs/proc/array.c: allow reporting eip/esp for all coredumping threads Date: Tue, 2 Jul 2019 10:01:56 +0200 Message-Id: <20190702080124.632413849@linuxfoundation.org> X-Mailer: git-send-email 2.22.0 In-Reply-To: <20190702080123.904399496@linuxfoundation.org> References: <20190702080123.904399496@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org From: John Ogness commit cb8f381f1613cafe3aec30809991cd56e7135d92 upstream. 0a1eb2d474ed ("fs/proc: Stop reporting eip and esp in /proc/PID/stat") stopped reporting eip/esp and fd7d56270b52 ("fs/proc: Report eip/esp in /prod/PID/stat for coredumping") reintroduced the feature to fix a regression with userspace core dump handlers (such as minicoredumper). Because PF_DUMPCORE is only set for the primary thread, this didn't fix the original problem for secondary threads. Allow reporting the eip/esp for all threads by checking for PF_EXITING as well. This is set for all the other threads when they are killed. coredump_wait() waits for all the tasks to become inactive before proceeding to invoke a core dumper. Link: http://lkml.kernel.org/r/87y32p7i7a.fsf@linutronix.de Link: http://lkml.kernel.org/r/20190522161614.628-1-jlu@pengutronix.de Fixes: fd7d56270b526ca3 ("fs/proc: Report eip/esp in /prod/PID/stat for coredumping") Signed-off-by: John Ogness Reported-by: Jan Luebbe Tested-by: Jan Luebbe Cc: Alexey Dobriyan Cc: Andy Lutomirski Cc: Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds Signed-off-by: Greg Kroah-Hartman --- fs/proc/array.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/fs/proc/array.c +++ b/fs/proc/array.c @@ -448,7 +448,7 @@ static int do_task_stat(struct seq_file * a program is not able to use ptrace(2) in that case. It is * safe because the task has stopped executing permanently. */ - if (permitted && (task->flags & PF_DUMPCORE)) { + if (permitted && (task->flags & (PF_EXITING|PF_DUMPCORE))) { if (try_get_task_stack(task)) { eip = KSTK_EIP(task); esp = KSTK_ESP(task);