Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1082086yba; Thu, 4 Apr 2019 04:01:04 -0700 (PDT) X-Google-Smtp-Source: APXvYqyOHCOUI+tjBhJJrW8UUhFZ2gTc99y/xqfkwUTAfLcelIKJgG61Nw3yhADQha3MUMWCqesc X-Received: by 2002:a62:1d0d:: with SMTP id d13mr5246401pfd.96.1554375664586; Thu, 04 Apr 2019 04:01:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554375664; cv=none; d=google.com; s=arc-20160816; b=aym42hedVFXH9czuUSq/R3xTMYatcWh80Y9H9LvrO2sIzpBfP1vCpdMokrt5A6m3aW /hqe4UWz+5d8tfPySWyDfGUPucIo9+bUMr4wIUpDhPd7Ymx4v6OYjpQ6Fewrez07Om+e d+2V/pXd4mJ1/htAtbqKQ4XKE9BQR/7qJvNZ4ByO0Yjgt83weHNnsu4VtEL0e/SEQjZ3 +Lcb5uFwWFeYfVjFvTjwmxRxnO0z6URzVU4isB28QEl0iczy4QlBu5epPqfx6auh8hEQ KhFyn2JlKxMDu8FjZC/2b2gdbUU7N5NCohPAciK9RVhzKytVo1dVEKPDf+TV0BZe6ARx NtyQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=pEWR5oe71t/yysCeO9RgKqxk1row98djDOlrlZCLS/c=; b=smjaUdipxLWf8FdM75V9Rx7hC2Um/9WZzr2XlkSrtfKFR1bXBAvqNRgi/i6+b4yPi2 VMZYg0DvHUOEX+iI3v00fE5jmpc5phxtpxIslt1gkopLpzDvL/ffTQIp6w3c/QUt9uRD cu5gWn/qcLQbjWtbMdyHpdO0AGFaaAKbdHzRb3af7y12ecj+8TU4sX7pjar4l2TB5G9L 2txBEfQKC8jq0b2CRPwfJCiI2b/r9dvIdEl3MHi0RKNZGriDMRZ8EcGgQoAVxuXj6j0V L2fVdZll1GUBATiFYOtvY7POo5J0qkejL+OZC4+TzBreEjZ6KGP9nbwnk2Ggg7zVHGxB +19w== 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 h11si8970156pgv.163.2019.04.04.04.00.48; Thu, 04 Apr 2019 04:01:04 -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 S1729854AbfDDK7g (ORCPT + 99 others); Thu, 4 Apr 2019 06:59:36 -0400 Received: from mx2.suse.de ([195.135.220.15]:45562 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728345AbfDDK7e (ORCPT ); Thu, 4 Apr 2019 06:59:34 -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 6B8AFAC32; Thu, 4 Apr 2019 10:59:32 +0000 (UTC) Date: Thu, 4 Apr 2019 12:59:30 +0200 (CEST) From: Miroslav Benes To: Joe Lawrence cc: Joao Moreira , live-patching@vger.kernel.org, pmladek@suse.cz, jikos@suse.cz, nstange@suse.de, jpoimboe@redhat.com, khlebnikov@yandex-team.ru, jeyu@kernel.org, matz@suse.de, linux-kernel@vger.kernel.org, yamada.masahiro@socionext.com, linux-kbuild@vger.kernel.org, michal.lkml@markovi.net Subject: Re: [PATCH v2 2/8] kbuild: Support for Symbols.list creation In-Reply-To: Message-ID: References: <20190301141313.15057-1-jmoreira@suse.de> <20190301141313.15057-3-jmoreira@suse.de> <20190318191926.GA23138@redhat.com> <5f615af5-ced7-2361-5b71-71fece8b43c5@suse.de> <699e78da-36ba-8217-c509-2e9b443bd380@suse.de> <1b6ee81b-5699-a1cc-9a85-02df0eeaed12@redhat.com> <20190328201703.GA8658@redhat.com> <20190401193529.GA26375@redhat.com> User-Agent: Alpine 2.21 (LSU 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 3 Apr 2019, Miroslav Benes wrote: > > > > Hmm, maybe I spoke too soon. > > > > > > I am having issues if I have a two-object livepatch module in which each > > > object file needs to specify its own KLP_MODULE_RELOC for the same > > > symbol name. > > > > > > For example: I have test_klp_convert.ko which is comprised of > > > test_klp_convert_a.o. which needs to refer to state_show,1 and > > > test_klp_convert_b.o. which needs to refer to state_show,2. > > > > > > % make > > > ... > > > KLP lib/livepatch/test_klp_convert.ko > > > klp-convert: Conflicting KLP_SYMPOS definition: vmlinux.state_show,0 vs. vmlinux.state_show,1. > > > klp-convert: Unable to load user-provided sympos > > > make[2]: *** [scripts/Makefile.modpost:148: lib/livepatch/test_klp_convert.ko] Error 255 > > > make[1]: *** [/home/cloud-user/disk/linux/Makefile:1282: modules] Error 2 > > > make: *** [Makefile:170: sub-make] Error 2 > > > > > > I take a closer look next week, but in the meantime, see the source > > > files below. > > > > Okay, with a fresh set of eyes today, I think the issue can be > > summarized as: > > > > * "Special" livepatch symbols, as processed by klp-convert, require > > external linkage, otherwise a new local storage instance will be > > created and miss klp-convert altogether > > > > * When linking together two object files, their combined symbol table > > will include a de-duped list of uniquly named global symbols > > > > So if we are to run klp-convert on the combined module object file (as > > per v2 plus suggested changes in this thread), we are going to run into > > problems if ... > > > > > > Example > > ======= > > > > (quoted in previous reply), test_klp_convert_a and test_klp_convert_b > > have their own "state_show" variable in which each wishes to resolve to > > unique symbol positions (2 and 3 accordingly). > > > > > > test_klp_convert_a > > ------------------ > > > > We get one symbol table entry and one relocation as expected. > > > > % eu-readelf --symbols lib/livepatch/test_klp_convert_a.o > > > > Symbol table [27] '.symtab' contains 38 entries: > > 29 local symbols String table: [28] '.strtab' > > Num: Value Size Type Bind Vis Ndx Name > > ... > > 30: 0000000000000000 0 NOTYPE GLOBAL DEFAULT UNDEF state_show > > ... > > > > % eu-readelf --relocs lib/livepatch/test_klp_convert_a.o > > > > Relocation section [12] '.rela.klp.module_relocs.vmlinux' for section [11] '.klp.module_relocs.vmlinux' at offset 0x4b8 contains 1 entry: > > Offset Type Value Addend Name > > 000000000000000000 X86_64_64 000000000000000000 +0 state_show > > > > > > test_klp_convert_b > > ------------------ > > > > Just like the other object file, one symbol table entry and one > > relocation: > > > > % eu-readelf --symbols lib/livepatch/test_klp_convert_a.o > > Symbol table [24] '.symtab' contains 23 entries: > > 19 local symbols String table: [25] '.strtab' > > Num: Value Size Type Bind Vis Ndx Name > > ... > > 20: 0000000000000000 0 NOTYPE GLOBAL DEFAULT UNDEF state_show > > ... > > > > % eu-readelf --relocs lib/livepatch/test_klp_convert_b.o > > > > Relocation section [ 9] '.rela.klp.module_relocs.vmlinux' for section [ 8] '.klp.module_relocs.vmlinux' at offset 0x118 contains 1 entry: > > Offset Type Value Addend Name > > 000000000000000000 X86_64_64 000000000000000000 +0 state_show > > > > > > test_klp_convert > > ---------------- > > > > But the combined test_klp_convert.klp.o file has only a single > > unresolved "state_show" symbol in its symbol table: > > > > % eu-readelf --symbols lib/livepatch/test_klp_convert.klp.o > > > > Symbol table [35] '.symtab' contains 57 entries: > > 47 local symbols String table: [36] '.strtab' > > Num: Value Size Type Bind Vis Ndx Name > > ... > > 52: 0000000000000000 0 NOTYPE GLOBAL DEFAULT UNDEF state_show > > ... > > > > though the .rela.klp.module_relocs.vmlinux relocation section has two > > entries: > > > > % eu-readelf --relocs lib/livepatch/test_klp_convert.klp.o > > > > Relocation section [17] '.rela.klp.module_relocs.vmlinux' for section [16] '.klp.module_relocs.vmlinux' at offset 0x446c8 contains 2 entries: > > Offset Type Value Addend Name > > 000000000000000000 X86_64_64 000000000000000000 +0 state_show > > 0x0000000000000010 X86_64_64 000000000000000000 +0 state_show > > > > and it looks like the combined KLP_MODULE_RELOC still contains the two > > unique symbol position values (2 and 3): > > > > % objcopy -O binary --only-section=.klp.module_relocs.vmlinux lib/livepatch/test_klp_convert.klp.o >(hexdump -C) > > 00000000 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 |................| > > 00000010 00 00 00 00 00 00 00 00 03 00 00 00 |............| > > 0000001c > > Nice :/ > > > Maybe we can work around this by modifying the annotation macros and/or > > klp-convert, or live with this for now. > > The question is (and I'll check later. I cannot wrap my head around it > now) if it at least works if there are two references of the same symbol > in two different .o. It would be same state_show in this case and not two > different ones. If it works then I think we can live with it for a while, > because after all duplicate symbols are quite rare in the kernel. I think it should work. There is only one case which causes problems. There exists an ambiguous local symbol in one parent object and a livepatch needs to reference two (or more) different versions of the symbol. In that case there have to be more sympos records provided by a user to help klp-convert distinguish between the cases. klp-convert is of course confused because it currently cannot cope with that. All other cases should be fine (theoretically). So we need to come up with a solution which would help klp-convert recognize the cases (symbol usage sites). Some sort of user annotation, but I cannot think of anything right now. Miroslav