From: Vincenzo Mezzela <vincenzo.mezzela@suse.com>
To: Jonathan Corbet <corbet@lwn.net>,
live-patching@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: jpoimboe@kernel.org, jikos@kernel.org, mbenes@suse.cz,
pmladek@suse.com, joe.lawrence@redhat.com
Subject: Re: [PATCH] docs: livepatch: move text out of code block
Date: Thu, 27 Feb 2025 17:12:42 +0100 [thread overview]
Message-ID: <e052eb20-09ff-4917-8841-95af889afd9e@suse.com> (raw)
In-Reply-To: <87bjunqtg8.fsf@trenco.lwn.net>
On 2/27/25 4:48 PM, Jonathan Corbet wrote:
> Vincenzo MEZZELA <vincenzo.mezzela@suse.com> writes:
>
>> Part of the documentation text is included in the readelf output code
>> block. Hence, split the code block and move the affected text outside.
>>
>> Signed-off-by: Vincenzo MEZZELA <vincenzo.mezzela@suse.com>
>> ---
>> Documentation/livepatch/module-elf-format.rst | 17 ++++++++++++-----
>> 1 file changed, 12 insertions(+), 5 deletions(-)
>>
>> diff --git a/Documentation/livepatch/module-elf-format.rst b/Documentation/livepatch/module-elf-format.rst
>> index a03ed02ec57e..eadcff224335 100644
>> --- a/Documentation/livepatch/module-elf-format.rst
>> +++ b/Documentation/livepatch/module-elf-format.rst
>> @@ -217,16 +217,23 @@ livepatch relocation section refer to their respective symbols with their symbol
>> indices, and the original symbol indices (and thus the symtab ordering) must be
>> preserved in order for apply_relocate_add() to find the right symbol.
>>
>> -For example, take this particular rela from a livepatch module:::
>> +For example, take this particular rela from a livepatch module:
>> +
>> +::
>
> The right fix here is to just delete the extra ":"
>
>> Relocation section '.klp.rela.btrfs.text.btrfs_feature_attr_show' at offset 0x2ba0 contains 4 entries:
>> Offset Info Type Symbol's Value Symbol's Name + Addend
>> 000000000000001f 0000005e00000002 R_X86_64_PC32 0000000000000000 .klp.sym.vmlinux.printk,0 - 4
>>
>> - This rela refers to the symbol '.klp.sym.vmlinux.printk,0', and the symbol index is encoded
>> - in 'Info'. Here its symbol index is 0x5e, which is 94 in decimal, which refers to the
>> - symbol index 94.
>> - And in this patch module's corresponding symbol table, symbol index 94 refers to that very symbol:
>> +This rela refers to the symbol '.klp.sym.vmlinux.printk,0', and the symbol
>> +index is encoded in 'Info'. Here its symbol index is 0x5e, which is 94 in
>> +decimal, which refers to the symbol index 94.
>> +
>> +And in this patch module's corresponding symbol table, symbol index 94 refers
>> +to that very symbol:
>> +
>> +::
>
> You can put that extra colon here rather than introducing a separate
> "::" line.
>
Hi,
You are right. I'll send an updated version.
Thanks for the feedback,
Vincenzo
prev parent reply other threads:[~2025-02-27 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 15:03 Vincenzo MEZZELA
2025-02-27 15:48 ` Jonathan Corbet
2025-02-27 16:12 ` Vincenzo Mezzela [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e052eb20-09ff-4917-8841-95af889afd9e@suse.com \
--to=vincenzo.mezzela@suse.com \
--cc=corbet@lwn.net \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®