From: "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>
To: "Venkateswararao Jujjuri \(JV\)" <jvrao@linux.vnet.ibm.com>,
v9fs-developer@lists.sourceforge.net
Cc: linux-fsdevel@vger.kernel.org,
"Venkateswararao Jujjuri \(JV\)" <jvrao@linux.vnet.ibm.com>
Subject: Re: [PATCH 1/2] [net/9p] Set the condition just before waking up.
Date: Tue, 15 Mar 2011 15:41:57 +0530 [thread overview]
Message-ID: <8739mor8uq.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <1300140761-8769-1-git-send-email-jvrao@linux.vnet.ibm.com>
On Mon, 14 Mar 2011 15:12:41 -0700, "Venkateswararao Jujjuri (JV)" <jvrao@linux.vnet.ibm.com> wrote:
> Given that the sprious wake-ups are common, we need to move the
> condition setting right next to the wake_up().
I don't understand the above. What do you mean by spurious wakeups are
common ? I guess what happened was that when the work queue got woken up
via p9_client_cb, another request req->status was found to be received
(REQ_STATUS_RCVD) because we set it ahead. So it is not that spurious
wakeups are common, but rather it is a bug we had right ?
> After setting the condition
> to req->status = REQ_STATUS_RCVD, sprious wakeups may cause the
> virtqueue back on the free list for someone else to use.
> This may result in kernel panic while relasing the pinned pages
> in p9_release_req_pages().
But why are we doing that release pages in the req_done path. ? why not
after we wake up the sleeper in p9_client_rpc ?
-aneesh
prev parent reply other threads:[~2011-03-15 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 22:12 [PATCH 1/2] [net/9p] Set the condition just before waking up Venkateswararao Jujjuri (JV)
2011-03-15 10:11 ` Aneesh Kumar K. V [this message]
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=8739mor8uq.fsf@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=jvrao@linux.vnet.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=v9fs-developer@lists.sourceforge.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.