From: Li Wang <liwang@ubuntukylin.com>
To: John Spray <john.spray@inktank.com>, Sage Weil <sage@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: New Defects reported by Coverity Scan for ceph (fwd)
Date: Tue, 04 Mar 2014 08:53:16 +0800 [thread overview]
Message-ID: <531523FC.8070509@ubuntukylin.com> (raw)
In-Reply-To: <CAGd4Wr38czZ5REXmFaeniR8Umr9z-UN8sMrfMawh4ZF0pR_NhA@mail.gmail.com>
Then it seems that Coverity is only able to perform intra-procedure
check, is there any inter-procedure check option to turn on?
On 2014/3/4 6:53, John Spray wrote:
> On Mon, Mar 3, 2014 at 10:23 PM, Sage Weil <sage@inktank.com> wrote:
>> ** CID 1188299: Data race condition (MISSING_LOCK)
>> /mds/MDSUtility.cc: 142 in MDSUtility::handle_mds_map(MMDSMap *)()
>
> Is there a trick to getting coverity to realise that the lock is held,
> but by the calling function? Does it recognise assertions that the
> lock is held?
>
> Cheers,
> John
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2014-03-04 0:53 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 22:23 New Defects reported by Coverity Scan for ceph (fwd) Sage Weil
2014-03-03 22:53 ` John Spray
2014-03-04 0:53 ` Li Wang [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-08 14:59 Sage Weil
2014-09-30 13:59 Sage Weil
2014-09-30 17:26 ` Loic Dachary
2014-09-30 17:36 ` Gregory Farnum
2014-09-30 17:38 ` Sage Weil
2014-09-30 17:41 ` Ric Wheeler
2014-09-25 15:02 Sage Weil
2014-09-25 15:27 ` John Spray
2014-09-16 21:44 Sage Weil
2014-08-23 16:04 Sage Weil
2014-07-11 3:39 Sage Weil
2014-06-20 14:46 Sage Weil
2014-06-07 16:12 Sage Weil
2014-06-08 8:38 ` Sebastien Ponce
2014-06-18 7:37 ` Sebastien Ponce
2014-06-06 15:54 Sage Weil
2014-05-30 13:54 Sage Weil
2014-05-20 16:16 Sage Weil
2014-05-10 16:03 Sage Weil
2014-04-22 15:26 Sage Weil
2014-04-12 4:06 Sage Weil
2014-04-12 8:26 ` Loic Dachary
2013-12-17 17:10 Sage Weil
2013-12-16 16:07 Sage Weil
2013-12-17 9:01 ` Ilya Dryomov
2013-08-21 4:09 Sage Weil
2013-07-25 20:31 Sage Weil
2013-07-19 18:04 Sage Weil
2013-06-19 19:36 Sage Weil
2013-06-19 21:03 ` Loic Dachary
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=531523FC.8070509@ubuntukylin.com \
--to=liwang@ubuntukylin.com \
--cc=ceph-devel@vger.kernel.org \
--cc=john.spray@inktank.com \
--cc=sage@inktank.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 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.