qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: "Andreas Färber" <afaerber@suse.de>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Peter Crosthwaite" <peter.crosthwaite@xilinx.com>,
	"Hervé Poussineau" <hpoussin@reactos.org>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	"Igor Mammedov" <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] qom: detect bad reentrance during object_class_foreach
Date: Fri, 20 Dec 2013 22:43:05 +1100	[thread overview]
Message-ID: <52B42D49.9060402@ozlabs.ru> (raw)
In-Reply-To: <52B429FD.3040800@suse.de>

On 12/20/2013 10:29 PM, Andreas Färber wrote:
> Am 19.12.2013 12:38, schrieb Alexey Kardashevskiy:
>> On 12/16/2013 08:23 AM, Andreas Färber wrote:
>>> Am 04.12.2013 06:51, schrieb Peter Crosthwaite:
>>>> On Wed, Dec 4, 2013 at 1:42 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>>>> From: Hervé Poussineau <hpoussin@reactos.org>
>>>>>
>>>>> We should not modify the type hash table while it is being iterated on.
>>>>> Assert that it does not happen.
>>>>>
>>>>> Signed-off-by: Hervé Poussineau <hpoussin@reactos.org>
>>>>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>>>>> ---
>>>>>  qom/object.c | 4 ++++
>>>>>  1 file changed, 4 insertions(+)
>>>>>
>>>>> diff --git a/qom/object.c b/qom/object.c
>>>>> index 3a43186..1dee9f0 100644
>>>>> --- a/qom/object.c
>>>>> +++ b/qom/object.c
>>>>> @@ -78,8 +78,10 @@ static GHashTable *type_table_get(void)
>>>>>      return type_table;
>>>>>  }
>>>>>
>>>>> +static bool enumerating = false;
>>>>
>>>> Global variable could probably use a more descriptive name.
>>>
>>> I renamed it to enumerating_types and dropped the assignment as
>>> suggested elsewhere by Alexey (a reply here would've been nice!).
>>
>> Whose reply? To what? :)
> 
> A reply of yours to Peter C.'s change request, stating that you have
> addressed it - and in this case in which series. :)

You lost me here. I got these patches from Paolo Bonzini and I was told to
repost them together with my other patches, that's it :)


>>> I also took the liberty of inserted a white line to make the function
>>> better readable.
>>
>> I do not mind, this was not my stuff :)
>>
>> What I wonder about is what is going to happen to the rest of what I
>> posted? Should I wait till this qom-next gets merged to upstream and repost
>> my patches for Alex Graf again? Thanks.
> 
> I do intend to post a pull before Chistmas, reviewing+applying the last
> no_user patch from Markus was one key ingredient for that.
> 
> Not sure which rest exactly you're referring to? I need to review your
> latest QemuOpts proposal among others. Actually I have a whole A4 page
> written down with series I'm wading through. ;)


I posted the "[PATCH v4 0/8] spapr: bootindex support" series which
included the 2 patches you mentioned in this series, from the rest - 3 are
for spapr and 3 are platform independent.



-- 
Alexey

  reply	other threads:[~2013-12-20 11:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-03 15:41 [Qemu-devel] [PATCH 0/2] qom: fix registration of QOM interfaces Paolo Bonzini
2013-12-03 15:41 ` [Qemu-devel] [PATCH 1/2] qom: do not register interface "types" in the type table Paolo Bonzini
2013-12-03 15:42 ` [Qemu-devel] [PATCH 2/2] qom: detect bad reentrance during object_class_foreach Paolo Bonzini
2013-12-04  5:51   ` Peter Crosthwaite
2013-12-15 21:23     ` Andreas Färber
2013-12-19 11:38       ` Alexey Kardashevskiy
2013-12-20 11:29         ` Andreas Färber
2013-12-20 11:43           ` Alexey Kardashevskiy [this message]
2013-12-24  6:49             ` Alexey Kardashevskiy
2013-12-24 11:20               ` Andreas Färber
2013-12-15 21:25 ` [Qemu-devel] [PATCH 0/2] qom: fix registration of QOM interfaces Andreas Färber

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=52B42D49.9060402@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=afaerber@suse.de \
    --cc=hpoussin@reactos.org \
    --cc=imammedo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).