From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xenproject.org, tim@xen.org,
stefano.stabellini@citrix.com
Subject: Re: [PATCH for 4.5] xen/arm: Initialize the domain vgic lock
Date: Thu, 18 Dec 2014 12:26:02 +0000 [thread overview]
Message-ID: <5492C7DA.8050301@linaro.org> (raw)
In-Reply-To: <1418904755.11882.43.camel@citrix.com>
On 18/12/2014 12:12, Ian Campbell wrote:
> On Thu, 2014-12-18 at 12:05 +0000, Julien Grall wrote:
>> Hi Ian,
>>
>> On 18/12/2014 09:47, Ian Campbell wrote:
>>> On Wed, 2014-12-17 at 15:40 +0000, Julien Grall wrote:
>>>> The domain vgic lock is used uninitialized.
>>>>
>>>> Signed-off-by: Julien Grall <julien.grall@linaro.org>
>>>
>>> Acked-by: Ian Campbell <ian.campbell@citrix.com>
>>>
>>>> ---
>>>> This is a bug fix for Xen 4.5 and Xen 4.4. The vgic lock is used
>>>> unitialized. Luckily we only use the field "raw" which is reset to 0
>>>> during the domain allocation.
>>>>
>>>> There is no harm to apply for Xen 4.5 because it will correctly set
>>>> the spin_lock structure for a later usage.
>>>
>>> By your above reasoning there is also no point, is there? That said, I
>>> think we should take this since as you say it is harmless and good
>>> practice to initialise spinlocks even if not strictly necessary.
>>
>> It's necessary to initialize spinlocks, not all the field of the
>> spinlock is using the value 0 at initialization time.
>
> You said "...we only use the field "raw" which is reset to 0...". Was
> that statement inaccurate?
It's accurate in the current. I should have give more details earlier,
sorry.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-12-18 12:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 15:40 [PATCH for 4.5] xen/arm: Initialize the domain vgic lock Julien Grall
2014-12-18 9:47 ` Ian Campbell
2014-12-18 12:05 ` Julien Grall
2014-12-18 12:12 ` Ian Campbell
2014-12-18 12:26 ` Julien Grall [this message]
2014-12-19 14:23 ` Konrad Rzeszutek Wilk
2015-01-06 11:44 ` Ian Campbell
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=5492C7DA.8050301@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=tim@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.