From: "Jürgen Groß" <jgross@suse.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
clang-built-linux@googlegroups.com
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 1/2] xen/xenbus: avoid large structs and arrays on the stack
Date: Tue, 12 May 2020 11:13:27 +0200 [thread overview]
Message-ID: <aa93722b-100a-c750-cf51-bcaf9defbd03@suse.com> (raw)
In-Reply-To: <965e1d65-3a0c-3a71-ca58-2b5c04f98bce@oracle.com>
On 11.05.20 20:01, Boris Ostrovsky wrote:
> On 5/11/20 3:31 AM, Juergen Gross wrote:
>>
>> static int xenbus_map_ring_valloc_hvm(struct xenbus_device *dev,
>
>
> I wonder whether we can drop valloc/vfree from xenbus_ring_ops' names.
I can do that.
>
>
>> + struct map_ring_valloc *info,
>> grant_ref_t *gnt_ref,
>> unsigned int nr_grefs,
>> void **vaddr)
>> {
>> - struct xenbus_map_node *node;
>> + struct xenbus_map_node *node = info->node;
>> int err;
>> void *addr;
>> bool leaked = false;
>> - struct map_ring_valloc_hvm info = {
>> - .idx = 0,
>> - };
>> unsigned int nr_pages = XENBUS_PAGES(nr_grefs);
>>
>> - if (nr_grefs > XENBUS_MAX_RING_GRANTS)
>> - return -EINVAL;
>> -
>> - *vaddr = NULL;
>> -
>> - node = kzalloc(sizeof(*node), GFP_KERNEL);
>> - if (!node)
>> - return -ENOMEM;
>> -
>> err = alloc_xenballooned_pages(nr_pages, node->hvm.pages);
>> if (err)
>> goto out_err;
>>
>> gnttab_foreach_grant(node->hvm.pages, nr_grefs,
>> xenbus_map_ring_setup_grant_hvm,
>> - &info);
>> + info);
>>
>> err = __xenbus_map_ring(dev, gnt_ref, nr_grefs, node->handles,
>> - info.phys_addrs, GNTMAP_host_map, &leaked);
>> + info, GNTMAP_host_map, &leaked);
>> node->nr_handles = nr_grefs;
>>
>> if (err)
>> @@ -641,11 +654,13 @@ static int xenbus_map_ring_valloc_hvm(struct xenbus_device *dev,
>> spin_unlock(&xenbus_valloc_lock);
>>
>> *vaddr = addr;
>> + info->node = NULL;
>
>
> Is this so that xenbus_map_ring_valloc() doesn't free it accidentally?
Yes.
Juergen
next prev parent reply other threads:[~2020-05-12 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 7:31 [PATCH 0/2] xen/xenbus: some cleanups Juergen Gross
2020-05-11 7:31 ` [PATCH 1/2] xen/xenbus: avoid large structs and arrays on the stack Juergen Gross
2020-05-11 18:01 ` Boris Ostrovsky
2020-05-12 9:13 ` Jürgen Groß [this message]
2020-05-11 7:31 ` [PATCH 2/2] xen/xenbus: let xenbus_map_ring_valloc() return errno values only Juergen Gross
2020-05-11 18:32 ` Boris Ostrovsky
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=aa93722b-100a-c750-cf51-bcaf9defbd03@suse.com \
--to=jgross@suse.com \
--cc=arnd@arndb.de \
--cc=boris.ostrovsky@oracle.com \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.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 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®