Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp1617209ybb; Thu, 9 Apr 2020 05:54:15 -0700 (PDT) X-Google-Smtp-Source: APiQypIPhbNibaSA8TK9Y/EeqfXPHqt2AI+WZkHpAejxwGPX9a0LIi7Z2s8ZnBxt564zfHJBN+rh X-Received: by 2002:a0c:ff06:: with SMTP id w6mr12374348qvt.143.1586436855529; Thu, 09 Apr 2020 05:54:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586436855; cv=none; d=google.com; s=arc-20160816; b=y/8vM4vie7pZOgzfcmFFKnX96lCuizodLcHZVG45rcPfhWnlHMdoqbNWnZux8vC+lZ vAFxcDOCsUoExc05TchHgkw/jAqqG0bkxwOP2ABdm9wuE/mBprcK/3ygEHcIausNrcTF fWsfqyBvTx13sohGZb3RcQrtfwmOXHfweUzsHEi+yxdd6UM4rkEAwFtF2RTZdpfwiyWG wifbrxprr8ALhilW8mbuwyKSEB22KU5vbNKbC5GzNhx59Oh+xl0a6v9mYJYYKEVHy/th 0qqJ0gvxirfa1tu01qmc8+68dd/kYIdtBAes66t/AtSTu/h+6Qrb9ecyevg/f7U2ukYx IZMQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=TZmA4pg3k+dyxdTvM3mLXWLto6f/ClFLBXh8mPitEPY=; b=l8tEcbUoPBTdOTAe7Jwb3Jco3a24gwHyS/AB3cP2JWQ8UcRCD20fXZm2qu4Ge4Dj1Q 67YcTvt+H1n23F85C9YfXoDn0nz6svTSVr7Bsxla/kClS5fOAbF7IwPRvtCBfnamaf+I aB54Pb8TwGLFBu4GmXLo+Jbfkxj2qjDoTN5GjlC8M4DSl8zNERdZZVtnr7+KlAoaDbhC oUbMsD73lyxR6YQI9gKnoWAj0AgckpCgB2DrKmf463zc9yhoZmybewsv/OCHHrF8dG5M Lxkw98grQFMSsaQaqPR835260dqEwHIEgxtlnUq05de6Nlz614YUZQBGXsIN1usfB7Jh VfpA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="XNqd/rx4"; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q134si5686838qke.319.2020.04.09.05.53.59; Thu, 09 Apr 2020 05:54:15 -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; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="XNqd/rx4"; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726650AbgDIMvi (ORCPT + 99 others); Thu, 9 Apr 2020 08:51:38 -0400 Received: from us-smtp-2.mimecast.com ([207.211.31.81]:55922 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725971AbgDIMvi (ORCPT ); Thu, 9 Apr 2020 08:51:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1586436697; 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: in-reply-to:in-reply-to:references:references; bh=TZmA4pg3k+dyxdTvM3mLXWLto6f/ClFLBXh8mPitEPY=; b=XNqd/rx4YHhvsg8MElpjXixeAA22IWfeWEU2ihOLAJS9TYalgca9HPGExqkoCodeqpUqqA 3kgIMlVPIuPcticglP6/ijNBQdhAt9gtjNgZtXUxHvpjpXrKbtYJqBwttRbNjU/oyOCbZm zpwx0iO4Pps9d+dgz8Z7bUoAjmDdJgU= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-325-3C-E88M4NfWluUW743yx3A-1; Thu, 09 Apr 2020 08:51:33 -0400 X-MC-Unique: 3C-E88M4NfWluUW743yx3A-1 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 5899119067E4; Thu, 9 Apr 2020 12:51:32 +0000 (UTC) Received: from bfoster (dhcp-41-2.bos.redhat.com [10.18.41.2]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 73F2A9DD87; Thu, 9 Apr 2020 12:51:27 +0000 (UTC) Date: Thu, 9 Apr 2020 08:51:25 -0400 From: Brian Foster To: Arnd Bergmann Cc: "Darrick J. Wong" , linux-xfs@vger.kernel.org, Christoph Hellwig , Dave Chinner , Eric Sandeen , Masahiro Yamada , linux-kernel@vger.kernel.org Subject: Re: [PATCH] xfs: stop CONFIG_XFS_DEBUG from changing compiler flags Message-ID: <20200409125125.GA38767@bfoster> References: <20200409080909.3646059-1-arnd@arndb.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200409080909.3646059-1-arnd@arndb.de> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 09, 2020 at 10:08:56AM +0200, Arnd Bergmann wrote: > I ran into a linker warning in XFS that originates from a mismatch > between libelf, binutils and objtool when certain files in the kernel > are built with "gcc -g": > > x86_64-linux-ld: fs/xfs/xfs_trace.o: unable to initialize decompress status for section .debug_info > > After some discussion, nobody could identify why xfs sets this flag > here. CONFIG_XFS_DEBUG used to enable lots of unrelated settings, but > now its main purpose is to enable extra consistency checks and assertions > that are unrelated to the debug info. > > Remove the Makefile logic to set the flag here. If anyone relies > on the debug info, this can simply be enabled again with the global > CONFIG_DEBUG_INFO option. > > Suggested-by: Christoph Hellwig > Link: https://lore.kernel.org/lkml/20200409074130.GD21033@infradead.org/ > Signed-off-by: Arnd Bergmann > --- Seems reasonable. Reviewed-by: Brian Foster > fs/xfs/Makefile | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/fs/xfs/Makefile b/fs/xfs/Makefile > index 4f95df476181..ff94fb90a2ee 100644 > --- a/fs/xfs/Makefile > +++ b/fs/xfs/Makefile > @@ -7,8 +7,6 @@ > ccflags-y += -I $(srctree)/$(src) # needed for trace events > ccflags-y += -I $(srctree)/$(src)/libxfs > > -ccflags-$(CONFIG_XFS_DEBUG) += -g > - > obj-$(CONFIG_XFS_FS) += xfs.o > > # this one should be compiled first, as the tracing macros can easily blow up > -- > 2.26.0 >