All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: ross.lagerwall@citrix.com, xen-devel@lists.xenproject.org
Subject: Re: [PATCH v4 1/9] livepatch: Clear .bss when payload is reverted
Date: Thu, 25 Aug 2016 17:08:16 +0100	[thread overview]
Message-ID: <99e2c349-e808-3fb1-eabd-7199bd99f592@citrix.com> (raw)
In-Reply-To: <57BD7D19020000780010881B@prv-mh.provo.novell.com>

On 24/08/16 09:55, Jan Beulich wrote:
>>>> On 24.08.16 at 04:22, <konrad.wilk@oracle.com> wrote:
>> --- a/xen/common/livepatch.c
>> +++ b/xen/common/livepatch.c
>> @@ -70,6 +70,9 @@ struct payload {
>>       unsigned int nsyms;                  /* Nr of entries in .strtab and symbols. */
>>       struct livepatch_build_id id;        /* ELFNOTE_DESC(.note.gnu.build-id) of the payload. */
>>       struct livepatch_build_id dep;       /* ELFNOTE_DESC(.livepatch.depends). */
>> +    void **bss;                          /* .bss's of the payload. */
>> +    size_t *bss_size;                    /* and their sizes. */
> Is size_t wide enough in the extreme case? Perhaps yes, because I
> don't think we'll ever load 64-bit ELF on a 32-bit platform.

Even if we did, there is no chance that more than a single size_t's 
worth of data needs clearing, or the payload wouldn't fit in the current 
virtual address space.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-08-25 16:08 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-24  2:22 [PATCH v4] Livepatch fixes and features for v4.8 Konrad Rzeszutek Wilk
2016-08-24  2:22 ` [PATCH v4 1/9] livepatch: Clear .bss when payload is reverted Konrad Rzeszutek Wilk
2016-08-24  8:55   ` Jan Beulich
2016-08-25 16:08     ` Andrew Cooper [this message]
2016-09-06 16:51       ` Konrad Rzeszutek Wilk
2016-09-07  9:18         ` Jan Beulich
2016-09-06 16:47     ` Konrad Rzeszutek Wilk
2016-09-07  8:02       ` Jan Beulich
2016-09-08  9:25         ` Konrad Rzeszutek Wilk
2016-09-09 13:33   ` Ross Lagerwall
2016-09-09 13:50     ` Konrad Rzeszutek Wilk
2016-09-09 13:58       ` Ross Lagerwall
2016-09-09 15:28       ` Jan Beulich
2016-08-24  2:22 ` [PATCH v4 2/9] livepatch: Deal with payloads without any .text Konrad Rzeszutek Wilk
2016-08-24  2:22 ` [PATCH v4 3/9] version/livepatch: Move xen_build_id_check to version.h Konrad Rzeszutek Wilk
2016-08-24  2:22 ` [PATCH v4 4/9] version: Print build-id at bootup Konrad Rzeszutek Wilk
2016-08-24  8:58   ` Jan Beulich
2016-09-06 16:57     ` Konrad Rzeszutek Wilk
2016-09-07  8:03       ` Jan Beulich
2016-09-09 13:37       ` Ross Lagerwall
2016-08-24  2:22 ` [PATCH v4 5/9] livepatch: Move code from prepare_payload to own routine Konrad Rzeszutek Wilk
2016-08-25 16:02   ` Ross Lagerwall
2016-08-24  2:22 ` [PATCH v4 6/9] livepatch: Add parsing for the symbol+0x<offset> Konrad Rzeszutek Wilk
2016-08-24  9:08   ` Jan Beulich
2016-09-06 19:56     ` Konrad Rzeszutek Wilk
2016-09-07  8:10       ` Jan Beulich
2016-09-08  9:22         ` Konrad Rzeszutek Wilk
2016-09-08 10:01           ` Jan Beulich
2016-09-09 14:28           ` Ross Lagerwall
2016-08-24  2:22 ` [PATCH v4 7/9] livepatch: NOP if func->new_[addr] is zero Konrad Rzeszutek Wilk
2016-08-24  9:13   ` Jan Beulich
2016-09-06 20:05     ` Konrad Rzeszutek Wilk
2016-09-07  8:13       ` Jan Beulich
2016-08-24  2:22 ` [PATCH v4 8/9] symbols: Generate an xen-sym.map Konrad Rzeszutek Wilk
2016-08-24  9:16   ` Jan Beulich
2016-09-09 13:43   ` Ross Lagerwall
2016-08-24  2:22 ` [PATCH v4 9/9] livepach: Add .livepatch.hooks functions and test-case Konrad Rzeszutek Wilk
2016-09-06 17:22   ` Konrad Rzeszutek Wilk
2016-09-06 18:25     ` Andrew Cooper
2016-09-08  1:18       ` Konrad Rzeszutek Wilk

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=99e2c349-e808-3fb1-eabd-7199bd99f592@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=ross.lagerwall@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.