From: Hanna Reitz <hreitz@redhat.com>
To: "Philippe Mathieu-Daudé" <philippe.mathieu.daude@gmail.com>,
qemu-block@nongnu.org
Cc: Emanuele Giuseppe Esposito <eesposit@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, Akihiko Odaki <akihiko.odaki@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH for-7.0] main-loop: Disable GLOBAL_STATE_CODE() assertions
Date: Tue, 29 Mar 2022 12:38:30 +0200 [thread overview]
Message-ID: <9c34125b-875f-e3b2-c0d4-2f6a283deb5a@redhat.com> (raw)
In-Reply-To: <dab63073-d532-2795-fce4-77bd0839f578@gmail.com>
On 29.03.22 12:17, Philippe Mathieu-Daudé wrote:
> On 29/3/22 11:35, Hanna Reitz wrote:
>> These assertions are very useful for developers to find bugs, and so
>> they have indeed pointed us towards bugs already. For users, it is not
>> so useful to find these bugs. We should probably not enable them in
>> releases until we are sufficiently certain that they will not fire
>> during normal operation, unless something is going seriously wrong.
>>
>> For example, we have received a bug report that you cannot add an NBD
>> server on a BDS in an I/O thread with `-incoming defer`. I am sure this
>> is a real bug that needs investigation, but we do not really have that
>> time right now, so close to release, and so I would rather disable the
>> assertions to get time to investigate such reports.
>>
>> (I am just putting the link as "buglink" below, not "closes", because
>> disabling the assertion will not fix the likely underlying bug.)
>>
>> Buglink: https://gitlab.com/qemu-project/qemu/-/issues/945
>
> Also helps:
> https://gitlab.com/qemu-project/qemu/-/issues/926
>
>> Signed-off-by: Hanna Reitz <hreitz@redhat.com>
>> ---
>> include/qemu/main-loop.h | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/include/qemu/main-loop.h b/include/qemu/main-loop.h
>> index 7a4d6a0920..3bf8aeb3cd 100644
>> --- a/include/qemu/main-loop.h
>> +++ b/include/qemu/main-loop.h
>> @@ -272,7 +272,8 @@ bool qemu_in_main_thread(void);
>> /* Mark and check that the function is part of the global state
>> API. */
>> #define GLOBAL_STATE_CODE() \
>> do { \
>> - assert(qemu_in_main_thread()); \
>> + /* FIXME: Re-enable after 7.0 release */ \
>> + /* assert(qemu_in_main_thread()); */ \
>> } while (0)
>> /* Mark and check that the function is part of the I/O API. */
>
> Do you want me to cancel/repost my PR without this patch?
>
> https://lore.kernel.org/qemu-devel/20220328224012.32737-3-philippe.mathieu.daude@gmail.com/
I think we should let Peter take your PR first, as long as the
discussion on this is still out. I’d like to give it a couple more
hours, and as far as I understand, we definitely want yours.
(Taking mine will then cause me rebase conflicts and make it look weird,
but that’s not too bad for something that’s just a temporary band-aid
anyway.)
Hanna
next prev parent reply other threads:[~2022-03-29 10:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 9:35 [PATCH for-7.0] main-loop: Disable GLOBAL_STATE_CODE() assertions Hanna Reitz
2022-03-29 10:17 ` Philippe Mathieu-Daudé
2022-03-29 10:38 ` Hanna Reitz [this message]
2022-03-29 12:33 ` Emanuele Giuseppe Esposito
2022-03-29 15:03 ` Stefan Hajnoczi
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=9c34125b-875f-e3b2-c0d4-2f6a283deb5a@redhat.com \
--to=hreitz@redhat.com \
--cc=akihiko.odaki@gmail.com \
--cc=eesposit@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philippe.mathieu.daude@gmail.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).