[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081201173737.GC2506@balbir.in.ibm.com>
Date: Mon, 1 Dec 2008 23:07:37 +0530
From: Balbir Singh <balbir@...ux.vnet.ibm.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
Cc: "linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: BUG: scheduling while atomic: kswapd0/273/0x00000002
* Aneesh Kumar K.V <aneesh.kumar@...ux.vnet.ibm.com> [2008-12-01 21:27:55]:
> On Mon, Dec 01, 2008 at 09:23:41PM +0530, Balbir Singh wrote:
> > * Aneesh Kumar K.V <aneesh.kumar@...ux.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);
>
Yes, I should have seen the stack. The same problem seems to exist for
ext3 as well (with log_wait_commit). kswapd() passes GFP_KERNEL as
gfp_mask in scan_control and that confuses the journalling layer,
since we hold the lock on page in shrink_page_list().
--
Balbir
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists