All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jürgen Groß" <jgross@suse.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Stefano Stabellini" <sstabellini@kernel.org>,
	"Julien Grall" <julien@xen.org>, "Wei Liu" <wl@xen.org>,
	"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
	"George Dunlap" <George.Dunlap@eu.citrix.com>,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Ian Jackson" <ian.jackson@eu.citrix.com>,
	xen-devel@lists.xenproject.org,
	"Daniel De Graaf" <dgdegra@tycho.nsa.gov>,
	"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH v5 3/8] xen: add basic hypervisor filesystem support
Date: Thu, 20 Feb 2020 10:07:06 +0100	[thread overview]
Message-ID: <7b6cf661-f3bb-bf3c-b322-d7b23d70fad2@suse.com> (raw)
In-Reply-To: <c47fc2c4-6b72-13eb-1cd3-c247c739d21f@suse.com>

On 20.02.20 09:43, Jan Beulich wrote:
> On 20.02.2020 08:27, Jürgen Groß wrote:
>> On 19.02.20 16:49, Jan Beulich wrote:
>>> On 19.02.2020 09:11, Juergen Gross wrote:
>>>> +static inline void hypfs_string_set(struct hypfs_entry_leaf *leaf,
>>>> +                                    const char *str)
>>>> +{
>>>> +    leaf->content = str;
>>>> +    leaf->e.size = strlen(str) + 1;
>>>> +}
>>>
>>> This looks at least risky to me, as the function name does in
>>> no way indicate that no copy of the string will be made. Hence
>>> its use with e.g. .init.rodata contents or a stack variable
>>> will not produce the intended result.
>>
>> Okay, what about naming it hypfs_string_set_reference() ?
> 
> Hmm, a little better because of drawing more attention to it
> due to the longish name. I'd be curious what others think here,
> in particular towards the alternative of actually allocating
> space and copying the string. If it is to remain as it is,
> while the function body is small I still think you also want to
> attach a comment to call out this behavior.

Okay.


Juergen


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

  reply	other threads:[~2020-02-20  9:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-19  8:11 [Xen-devel] [PATCH v5 0/8] Add hypervisor sysfs-like support Juergen Gross
2020-02-19  8:11 ` [Xen-devel] [PATCH v5 1/8] xen: add a generic way to include binary files as variables Juergen Gross
2020-02-19 12:05   ` Wei Liu
2020-02-19  8:11 ` [Xen-devel] [PATCH v5 2/8] docs: add feature document for Xen hypervisor sysfs-like support Juergen Gross
2020-02-19  8:11 ` [Xen-devel] [PATCH v5 3/8] xen: add basic hypervisor filesystem support Juergen Gross
2020-02-19 15:49   ` Jan Beulich
2020-02-19 16:19     ` Julien Grall
2020-02-20  7:27     ` Jürgen Groß
2020-02-20  8:43       ` Jan Beulich
2020-02-20  9:07         ` Jürgen Groß [this message]
2020-02-19 16:26   ` Julien Grall
2020-02-19 16:47     ` Julien Grall
2020-02-20  7:29     ` Jürgen Groß
2020-02-19  8:11 ` [Xen-devel] [PATCH v5 4/8] libs: add libxenhypfs Juergen Gross
2020-02-19  8:11 ` [Xen-devel] [PATCH v5 5/8] tools: add xenfs tool Juergen Gross
2020-02-19  8:11 ` [Xen-devel] [PATCH v5 6/8] xen: provide version information in hypfs Juergen Gross
2020-02-19  8:11 ` [Xen-devel] [PATCH v5 7/8] xen: add /buildinfo/config entry to hypervisor filesystem Juergen Gross
2020-02-19 15:57   ` Jan Beulich
2020-02-20  6:13     ` Jürgen Groß
2020-02-19  8:11 ` [Xen-devel] [PATCH v5 8/8] xen: add runtime parameter access support to hypfs Juergen Gross
2020-02-19 16:44   ` Jan Beulich
2020-02-20  8:22     ` Jürgen Groß
2020-02-20  8:49       ` Jan Beulich
2020-02-20  9:11         ` Jürgen Groß

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=7b6cf661-f3bb-bf3c-b322-d7b23d70fad2@suse.com \
    --to=jgross@suse.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=konrad.wilk@oracle.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=wl@xen.org \
    --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.