linux-ext4 - Re: BUG: scheduling while atomic: kswapd0/273/0x00000002

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <49348174.6060304@jp.fujitsu.com>
Date:	Tue, 02 Dec 2008 09:29:40 +0900
From:	Toshiyuki Okajima <toshi.okajima@...fujitsu.com>
To:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
CC:	Balbir Singh <balbir@...ux.vnet.ibm.com>,
	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: BUG: scheduling while atomic: kswapd0/273/0x00000002

Aneesh Kumar K.V wrote:
> 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);
> 
> -aneesh
OK. This problem was caused by the patch which I made.
I will make a patch which fixes it immediately.
Thank you for your report.

Best Regards,
Toshiyuki Okajima

--
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