From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: [PATCH 0/2] Coverity fixes for map_domain_page() mismatches
Date: Wed, 4 Dec 2013 15:09:14 +0000 [thread overview]
Message-ID: <1386169756-8406-1-git-send-email-andrew.cooper3@citrix.com> (raw)
In the most recent Coverity run, we submitted a modelling file which tried to
teach Coverity about map_domain_page() as allocating resource, and needing an
accompanying unmap_domain_page().
Here are two fixes directly identified by the modelling.
There were further issues identified, but I believe they are spurious and
caused by issues with the modelling itself.
There were also problems identified for tmem (which was the original cause of
trying to model this in the first place). As I have already submitted a patch
which is also a cleanup, it can be dealt with separately.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
next reply other threads:[~2013-12-04 15:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 15:09 Andrew Cooper [this message]
2013-12-04 15:09 ` [PATCH 1/2] amd/passthrough: Do not leak domain mappings from do_invalidate_dte() Andrew Cooper
2013-12-04 15:22 ` Jan Beulich
2013-12-04 15:30 ` Andrew Cooper
2013-12-04 16:44 ` [PATCH v2 " Andrew Cooper
2013-12-04 16:49 ` Jan Beulich
2013-12-04 17:59 ` [PATCH v3 " Andrew Cooper
2013-12-06 8:37 ` Jan Beulich
2013-12-09 10:08 ` Jan Beulich
2013-12-09 18:33 ` Suravee Suthikulanit
2013-12-09 18:34 ` Andrew Cooper
2013-12-09 18:41 ` [PATCH v4 " Andrew Cooper
2013-12-09 20:02 ` Suravee Suthikulpanit
2013-12-04 15:09 ` [PATCH 2/2] xen/page_alloc: Defer the domain mapping in scrub_one_page() Andrew Cooper
2013-12-04 15:23 ` Jan Beulich
2013-12-09 10:09 ` Jan Beulich
2013-12-09 11:02 ` Keir Fraser
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=1386169756-8406-1-git-send-email-andrew.cooper3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=xen-devel@lists.xen.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).