From: Dan Carpenter <dan.carpenter@oracle.com>
To: sage@newdream.net
Cc: ceph-devel@vger.kernel.org
Subject: re: ceph: cope with out of order (unsafe after safe) mds reply
Date: Mon, 10 Aug 2015 17:54:36 +0300 [thread overview]
Message-ID: <20150810145436.GA14295@mwanda> (raw)
Hello Sage Weil,
The patch 85792d0dd6e7: "ceph: cope with out of order (unsafe after
safe) mds reply" from May 13, 2010, leads to the following static
checker warning:
fs/ceph/mds_client.c:2414 handle_reply()
warn: we tested 'head->safe' before and it was 'false'
fs/ceph/mds_client.c
2406 /* dup? */
2407 if ((req->r_got_unsafe && !head->safe) ||
2408 (req->r_got_safe && head->safe)) {
^^^^^^^^^^^^^^^ ^^^^^^^^^^
If ->r_got_safe is set we always fail. If head->safe is set then we
fail here.
2409 pr_warn("got a dup %s reply on %llu from mds%d\n",
2410 head->safe ? "safe" : "unsafe", tid, mds);
2411 mutex_unlock(&mdsc->mutex);
2412 goto out;
2413 }
2414 if (req->r_got_safe && !head->safe) {
Otherwise we fail here. The only thing different is the error message.
2415 pr_warn("got unsafe after safe on %llu from mds%d\n",
2416 tid, mds);
2417 mutex_unlock(&mdsc->mutex);
2418 goto out;
2419 }
regards,
dan carpenter
reply other threads:[~2015-08-10 14:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150810145436.GA14295@mwanda \
--to=dan.carpenter@oracle.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@newdream.net \
/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.