Received: by 10.223.185.116 with SMTP id b49csp8826602wrg; Fri, 2 Mar 2018 08:35:41 -0800 (PST) X-Google-Smtp-Source: AG47ELuqEEa0DbggCvZvcTxiEVh6yszGC7UmpL2hTTfDJP37vMviTE6VCu5VeQrKfYHimL2rzktL X-Received: by 10.101.90.75 with SMTP id z11mr4898993pgs.29.1520008540986; Fri, 02 Mar 2018 08:35:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1520008540; cv=none; d=google.com; s=arc-20160816; b=VlhYHekiZ56G9R5M1/E0LfP8D4saNisZeb6aJL2qt0YYzzQGS5VbGYGzf+GrFnJeKk nfdE6IPRVwkWLnAgs3Gon6r6RzwHPbi12PqOGDEIBWfVC0CkHfZe3SuGUVQNutM1sGK/ w+jlose3oer8Ig+UL07AKS1Am0GMvd6DhvG0Db0IxbWe1VcPxN84ay3Ernxh0d/MvyJa Selg15ubbcuSzMMFDaLarz5TCD8A4tNzIFiMdFCMthmSuM/ls2kkzoVapVtJX9Kkq+PQ i8fichV4aKYqSssMEyrbOg9A7P3Ck2+zde+2RNfUjHv4Xwv6lEtMCp3Lb/NL6EPonJ6m lvLg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=ggvSrmnOVWdutrjGUtyBTl1BZuigRlMHk4zp7giyHA8=; b=buz/OLafx4u+cUZQ9ATbjS7F5R1HWKh8U5YJWdJNRvA4C6S7B9FEABvJut5hOU1KQJ 0jZjA0+7QKGgIvEjALjoeCnZhQMn1MHiXYmCM1vrZP8BPmCwXeWECHyQMWLRns0SWPDM 4URF9xc+pcOz5FDoDUPX40zUAlMyxLQk3hxRZjhTR0dZKSZXIu+CdxD2s8jjubiHL/9/ UlhVlphYvOgasE3VpYG6zENE+aqGfNXqfW5ZmVJtQTmEcWQM9DLFsAqK0xAfGySSM1Xa gWCAbIIkf9GoSe4FKOolFEskQJmplzCMOKPAF3NbsArtSPE0VVyE3HFxwEjnqX7eC3P+ rdrw== 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 d30-v6si4974661pld.452.2018.03.02.08.35.26; Fri, 02 Mar 2018 08:35:40 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1427971AbeCBPzL (ORCPT + 99 others); Fri, 2 Mar 2018 10:55:11 -0500 Received: from mx2.suse.de ([195.135.220.15]:45106 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1425921AbeCBPy6 (ORCPT ); Fri, 2 Mar 2018 10:54:58 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (charybdis-ext.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 58E10AD00; Fri, 2 Mar 2018 15:54:57 +0000 (UTC) Date: Fri, 2 Mar 2018 16:54:54 +0100 From: Petr Mladek To: Stephen Rothwell Cc: Linux-Next Mailing List , Linux Kernel Mailing List , Dave Young , Steven Rostedt , Sergey Senozhatsky , akpm@linux-foundation.org, Andi Kleen Subject: Re: linux-next: build failure after merge of the printk tree Message-ID: <20180302155454.eme5gplxdcltvwkw@pathway.suse.cz> References: <20180302160732.12691fbc@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180302160732.12691fbc@canb.auug.org.au> User-Agent: NeoMutt/20170421 (1.8.2) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 2018-03-02 16:07:32, Stephen Rothwell wrote: > Hi Petr, > > After merging the printk tree, today's linux-next build (bfin > BF518F-EZBRD_defconfig) failed like this: > > lib/dump_stack.o: In function `dump_stack': > lib/dump_stack.c:122: multiple definition of `dump_stack' > arch/blackfin/kernel/dumpstack.o:arch/blackfin/kernel/dumpstack.c:166: first defined here > > Presumably caused by commit > > 8040af489957 ("printk: move dump stack related code to lib/dump_stack.c") I could confirm that it is caused by this commit. I have temporary removed it from printk.git. > (Though it is not immediately obvious why.) It is a mistery to me. The error appears when I move any of dump_stack_print_info() or show_regs_print_info() function definitions from kernel/printk/printk.c to lib/dump_stack.c. All the other changes seems unrelated. The thing is that we basically do not touch dump_stack() definition by that patch. > This fails all the blackfin builds. nds32 (a new architecture) also > has a dump_stack function. Good to know! Best Regards, Petr