From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Balbir Singh <balbir@linux.vnet.ibm.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: BUG: scheduling while atomic: kswapd0/273/0x00000002
Date: Mon, 1 Dec 2008 21:27:55 +0530 [thread overview]
Message-ID: <20081201155755.GA30217@skywalker> (raw)
In-Reply-To: <20081201155341.GB2506@balbir.in.ibm.com>
On Mon, Dec 01, 2008 at 09:23:41PM +0530, Balbir Singh wrote:
> * Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> [2008-12-01 20:56:56]:
>
> > Hi,
> >
> > With the latest patch queue i am getting the below error
> >
>
> Did you enable jbd_debug enabled by any chance?
>
No. The problem is we cannot call jbd2_log_wait_commit
from blkdev_releasepage because jbd2_log_wait_commit
does a wait_event
549 spin_unlock(&journal->j_state_lock);
550 wait_event(journal->j_wait_done_commit,
551 !tid_gt(tid, journal->j_commit_sequence));
552 spin_lock(&journal->j_state_lock);
-aneesh
next prev parent reply other threads:[~2008-12-01 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 15:26 BUG: scheduling while atomic: kswapd0/273/0x00000002 Aneesh Kumar K.V
2008-12-01 15:53 ` Balbir Singh
2008-12-01 15:57 ` Aneesh Kumar K.V [this message]
2008-12-01 17:37 ` Balbir Singh
2008-12-02 0:29 ` Toshiyuki Okajima
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=20081201155755.GA30217@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.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).