Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp1914975imu; Sat, 10 Nov 2018 04:19:40 -0800 (PST) X-Google-Smtp-Source: AJdET5ctTI3rPN85YskPPcd61qaznfQlgxmepydvBEOsWjwnO3HJUnmsnCzQfrqIUEDdpacTMwWm X-Received: by 2002:a65:64d5:: with SMTP id t21-v6mr11160528pgv.428.1541852380633; Sat, 10 Nov 2018 04:19:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541852380; cv=none; d=google.com; s=arc-20160816; b=U8klI+Qz+2txome6xATMtwCca/ANp0AgmZEIlQqiB0stV0S1ThrVbgeYGaSqjNDwZ4 0v+8sFyjOsJTsgus6n9ZTB174LIS3Bhf7eS71nxSpuFDDjMgiQ1QiXc/8x3sNDUokG1E U/wsm5ULxQJrWIFkB6TG1Am3r9nwiPQguDNVYhm6FHcIGSq8iVX3i5fAWzRK8+/fWhVo hmZ71USYHEeWODhO2WXIvbgGFw9TpFeM86h77A96wk7V9Sodbba4JNvo2vDlXJbXo8yj 6NHY9Gvm3xWs8TZwjPW9zCpU9vKMFYRErdLS28cdjC9J4FUrnIcHcEsXO1VuzqOjXmrv R23A== 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; bh=ClPSGZoBrEB/oXsVwh+0vIkcFAU4wOFOBHF7DSPbPd4=; b=AZAnyHV9DYaZNjZdCABEFbLsADvQxCEBDGKtKdKI/wydoqXzdvKwsFZr5jBZjeLHXY K0LcUgYxo7usryAeZ7r+GPv2rT71ooZszANRBex2wmLsnDaf9HldI3DAPDEl6KjylxCW Xqe0nzaEYL3FrF0xi9FnN0zor3OsoaOt0i9Wuspe3d54ZWLRMPNbKjylxQegiTSNRMM1 +FSu7wy+dceyNQVXIdTNAw6QvO49N+sjqpmVhL2sAfl5GeWZZwv/4aXFEd7pagObzkjI kZRJz2Z2H6rlKWSAE1wLankE85cL7S4pvVkAyREbMmlVdXap+lUIQKFG5zeM0e4Ch+xI mhHA== 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; dmarc=fail (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 e69-v6si8193565pfg.5.2018.11.10.04.19.12; Sat, 10 Nov 2018 04:19: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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729074AbeKJWD2 (ORCPT + 99 others); Sat, 10 Nov 2018 17:03:28 -0500 Received: from mx1.redhat.com ([209.132.183.28]:38184 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728917AbeKJWD2 (ORCPT ); Sat, 10 Nov 2018 17:03:28 -0500 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id C298B81F12; Sat, 10 Nov 2018 12:18:37 +0000 (UTC) Received: from shodan.usersys.redhat.com (unknown [10.43.17.28]) by smtp.corp.redhat.com (Postfix) with ESMTP id 8BA6260150; Sat, 10 Nov 2018 12:18:37 +0000 (UTC) Received: by shodan.usersys.redhat.com (Postfix, from userid 1000) id BF6442C02E2; Sat, 10 Nov 2018 13:18:36 +0100 (CET) Date: Sat, 10 Nov 2018 13:18:36 +0100 From: Artem Savkov To: Josh Poimboeuf Cc: Peter Zijlstra , linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] objtool: fix .cold. functions parent symbols search Message-ID: <20181110121836.GG11183@shodan.usersys.redhat.com> References: <20181107202942.s24ej5mnh4b3mflw@treble> <20181107214515.9183-1-asavkov@redhat.com> <20181109172309.myxc2owh3k5v2wfb@treble> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20181109172309.myxc2owh3k5v2wfb@treble> User-Agent: Mutt/1.10.1 (2018-07-13) X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Sat, 10 Nov 2018 12:18:37 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 09, 2018 at 11:23:09AM -0600, Josh Poimboeuf wrote: > On Wed, Nov 07, 2018 at 10:45:15PM +0100, Artem Savkov wrote: > > Because find_symbol_by_name() traverses the same lists as read_symbols() > > changing sym->name in place without copying it affects the result of > > find_symbol_by_name() and, in case when ".cold" function precedes it's > > parent in sec->symbol_list, can result in function being considered a > > parent of itself. This leads to function length being set to 0 and other > > consequent side-effects including a segfault in add_switch_table(). > > The effects of this bug are only visible when building with > > -ffunction-sections in KCFLAGS. > > > > Fix by copying the search string instead of modifying it in place. > > > > Signed-off-by: Artem Savkov > > This needs a "Fixes" tag to identify the patch which introduced the bug. Ok, will do. > > --- > > tools/objtool/elf.c | 7 ++++--- > > 1 file changed, 4 insertions(+), 3 deletions(-) > > > > diff --git a/tools/objtool/elf.c b/tools/objtool/elf.c > > index 6dbb9fae0f9d..781c8afb29b9 100644 > > --- a/tools/objtool/elf.c > > +++ b/tools/objtool/elf.c > > @@ -298,6 +298,7 @@ static int read_symbols(struct elf *elf) > > /* Create parent/child links for any cold subfunctions */ > > list_for_each_entry(sec, &elf->sections, list) { > > list_for_each_entry(sym, &sec->symbol_list, list) { > > + char *pname; > > if (sym->type != STT_FUNC) > > continue; > > sym->pfunc = sym->cfunc = sym; > > @@ -305,9 +306,9 @@ static int read_symbols(struct elf *elf) > > if (!coldstr) > > continue; > > > > - coldstr[0] = '\0'; > > - pfunc = find_symbol_by_name(elf, sym->name); > > - coldstr[0] = '.'; > > + pname = strndup(sym->name, coldstr - sym->name); > > + pfunc = find_symbol_by_name(elf, pname); > > + free(pname); > > > > if (!pfunc) { > > WARN("%s(): can't find parent function", > > strndup()'s return code needs to be checked. > > Also, for such a short-lived allocation, I think a stack-allocated > string would be better. Hm, there seems to be no limit on lengths of strings in string table. What size would you consider reasonable for this stack-allocated string? -- Regards, Artem