From: Paolo Bonzini <pbonzini@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 01/11] blockjob: remove unnecessary check
Date: Wed, 19 Apr 2017 18:12:20 +0200 [thread overview]
Message-ID: <83bc60d2-c20f-1023-5337-b39b50a7fd6e@redhat.com> (raw)
In-Reply-To: <25c60922-5cb3-99c4-dd60-05bf1b6faca4@redhat.com>
On 19/04/2017 17:48, Eric Blake wrote:
>> bool block_job_user_paused(BlockJob *job)
>> {
> Is it worth using some form of attribute((nonnull)) annotations on
> various functions, to both state our intentions and let compilers help
> us catch obvious places where we are violating our intentions? That's
> more of a generic question to all of qemu, and doesn't affect your
> particular patch, other than your patch is an instance where the
> annotation would be useful if we wanted to use them.
What kind of bug would the compiler catch? I suppose Coverity would
catch all of them, and maybe -flto would as well.
Paolo
>> - return job ? job->user_paused : 0;
>> + return job->user_paused;
next prev parent reply other threads:[~2017-04-19 16:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 14:42 [Qemu-devel] [PATCH for 2.10 00/11] Preparation for block job mutex Paolo Bonzini
2017-04-19 14:42 ` [Qemu-devel] [PATCH 01/11] blockjob: remove unnecessary check Paolo Bonzini
2017-04-19 15:48 ` Eric Blake
2017-04-19 16:12 ` Paolo Bonzini [this message]
2017-04-19 16:16 ` Eric Blake
2017-04-24 23:19 ` John Snow
2017-04-26 8:36 ` Paolo Bonzini
2017-04-19 14:42 ` [Qemu-devel] [PATCH 02/11] blockjob: remove iostatus_reset callback Paolo Bonzini
2017-04-19 14:42 ` [Qemu-devel] [PATCH 03/11] blockjob: introduce block_job_early_fail Paolo Bonzini
2017-04-19 14:42 ` [Qemu-devel] [PATCH 04/11] blockjob: introduce block_job_pause/resume_all Paolo Bonzini
2017-04-19 14:42 ` [Qemu-devel] [PATCH 05/11] blockjob: separate monitor and blockjob APIs Paolo Bonzini
2017-04-24 23:24 ` John Snow
2017-05-04 10:50 ` Stefan Hajnoczi
2017-04-19 14:42 ` [Qemu-devel] [PATCH 06/11] blockjob: move iostatus reset inside block_job_user_resume Paolo Bonzini
2017-04-19 14:42 ` [Qemu-devel] [PATCH 07/11] blockjob: introduce block_job_cancel_async, check iostatus invariants Paolo Bonzini
2017-04-26 20:25 ` John Snow
2017-04-27 8:20 ` Paolo Bonzini
2017-05-04 10:53 ` Stefan Hajnoczi
2017-04-19 14:42 ` [Qemu-devel] [PATCH 08/11] blockjob: group BlockJob transaction functions together Paolo Bonzini
2017-04-24 23:46 ` John Snow
2017-05-04 10:53 ` Stefan Hajnoczi
2017-04-19 14:42 ` [Qemu-devel] [PATCH 09/11] blockjob: strengthen a bit test-blockjob-txn Paolo Bonzini
2017-04-19 14:42 ` [Qemu-devel] [PATCH 10/11] blockjob: reorganize block_job_completed_txn_abort Paolo Bonzini
2017-05-04 10:59 ` Stefan Hajnoczi
2017-04-19 14:42 ` [Qemu-devel] [PATCH 11/11] blockjob: use deferred_to_main_loop to indicate the coroutine has ended Paolo Bonzini
2017-05-04 11:07 ` Stefan Hajnoczi
2017-05-04 11:07 ` Stefan Hajnoczi
-- strict thread matches above, loose matches on Subject: below --
2017-05-08 14:12 [Qemu-devel] [PATCH v2 00/11] Preparation for block job mutex Paolo Bonzini
2017-05-08 14:13 ` [Qemu-devel] [PATCH 01/11] blockjob: remove unnecessary check Paolo Bonzini
2017-05-09 16:23 ` Jeff Cody
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=83bc60d2-c20f-1023-5337-b39b50a7fd6e@redhat.com \
--to=pbonzini@redhat.com \
--cc=eblake@redhat.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).