Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp4473277ybi; Tue, 11 Jun 2019 07:14:21 -0700 (PDT) X-Google-Smtp-Source: APXvYqyYmCWQBCGm5vtG/sDyqiXffcdpMqbNfWZf7ZoNf2Z8Dizleg3m3j5PE2Tkdq+lI/lVBp3+ X-Received: by 2002:a65:408d:: with SMTP id t13mr20183937pgp.373.1560262461248; Tue, 11 Jun 2019 07:14:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560262461; cv=none; d=google.com; s=arc-20160816; b=Y1ottUz792LGmjWGT4LNCMGuNF9Oz1xZ6Gy+CpbMF+Xu3uwY5qPQOngv5WkaZ8weZJ M7Q7ADoOQOuN1H1Ny1kyFXcvsZYsHUXrf0rfhi1gLSZXTN2EkqKaq576X0WFwYA6ZGlf qoG/FcjzGSzCLH4qllQFV2jKMz1kEuOtK2ADdQOCj+qMXsHFbwSWAOMj0h0zTCgc1cwn GX4NTTSjvcGAT6QiLR16E1kfbAahjrWFpePAhoVofdXu0tawGkDXYB/RyJeBGr/OUc8g eZfbEpIjju5sOAoUp2JnYrqSettCI1suVfTgBl2M1blvIV0uIYy/t/+GvzlfJwove0fZ lNNQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=oHOI+sgDx6165cT+aDHar2gyBSL7XRHiXW9paCSz+wc=; b=d4tr/g5TLKoV0/aUrvPFXiVdEExLQKphzocb8NigQSWGZbEu2W6w/35efCI8ptAb5N 2jSqJ34xhWfVV66ue7g+YWUGMG+55fOe2JGlsFSmBT6but5V+kfsK8NOWkaS64q/zp5r TUPNWGOiRhSTzSCfxY9okE5eCGWSFTYYoV6LO5Z5RVHyiznc4RsitPfZqr+idx8i1yqu VGlGDdX/K/Ts9Cr29FTv+fUpDCIE3oZM8IXJr9HzZ5HUsVqT9ipNZOFrSNoDKXoO5n9U 1qf7+UQrgeSNDuKZsZTLBj3gsJLijUYf8t8knpuMiZ4ZimGKjHbBnzrugbkg0puIpiUS mpDA== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id cj11si12879379plb.373.2019.06.11.07.14.04; Tue, 11 Jun 2019 07:14:21 -0700 (PDT) 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390026AbfFKONg (ORCPT + 99 others); Tue, 11 Jun 2019 10:13:36 -0400 Received: from mx2.suse.de ([195.135.220.15]:44152 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728309AbfFKON1 (ORCPT ); Tue, 11 Jun 2019 10:13:27 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 62D89AEEE; Tue, 11 Jun 2019 14:13:25 +0000 (UTC) From: Miroslav Benes To: jpoimboe@redhat.com, jikos@kernel.org, pmladek@suse.com Cc: joe.lawrence@redhat.com, kamalesh@linux.vnet.ibm.com, live-patching@vger.kernel.org, linux-kernel@vger.kernel.org, Miroslav Benes , Thomas Gleixner Subject: [PATCH v4 1/3] stacktrace: Remove weak version of save_stack_trace_tsk_reliable() Date: Tue, 11 Jun 2019 16:13:18 +0200 Message-Id: <20190611141320.25359-2-mbenes@suse.cz> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190611141320.25359-1-mbenes@suse.cz> References: <20190611141320.25359-1-mbenes@suse.cz> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Recent rework of stack trace infrastructure introduced a new set of helpers for common stack trace operations (commit e9b98e162aa5 ("stacktrace: Provide helpers for common stack trace operations") and related). As a result, save_stack_trace_tsk_reliable() is not directly called anywhere. Livepatch, currently the only user of the reliable stack trace feature, now calls stack_trace_save_tsk_reliable(). When CONFIG_HAVE_RELIABLE_STACKTRACE is set and depending on CONFIG_ARCH_STACKWALK, stack_trace_save_tsk_reliable() calls either arch_stack_walk_reliable() or mentioned save_stack_trace_tsk_reliable(). x86_64 defines the former, ppc64le the latter. All other architectures do not have HAVE_RELIABLE_STACKTRACE and include/linux/stacktrace.h defines -ENOSYS returning version for them. In short, stack_trace_save_tsk_reliable() returning -ENOSYS defined in include/linux/stacktrace.h serves the same purpose as the old weak version of save_stack_trace_tsk_reliable() which is therefore no longer needed. Cc: Thomas Gleixner Signed-off-by: Miroslav Benes --- kernel/stacktrace.c | 8 -------- 1 file changed, 8 deletions(-) diff --git a/kernel/stacktrace.c b/kernel/stacktrace.c index 36139de0a3c4..0c3f00db9069 100644 --- a/kernel/stacktrace.c +++ b/kernel/stacktrace.c @@ -255,14 +255,6 @@ save_stack_trace_regs(struct pt_regs *regs, struct stack_trace *trace) WARN_ONCE(1, KERN_INFO "save_stack_trace_regs() not implemented yet.\n"); } -__weak int -save_stack_trace_tsk_reliable(struct task_struct *tsk, - struct stack_trace *trace) -{ - WARN_ONCE(1, KERN_INFO "save_stack_tsk_reliable() not implemented yet.\n"); - return -ENOSYS; -} - /** * stack_trace_save - Save a stack trace into a storage array * @store: Pointer to storage array -- 2.21.0