[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201011072225.oA7MP38n001526@demeter1.kernel.org>
Date: Sun, 7 Nov 2010 22:25:03 GMT
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 22302] 2.6.36 BUG: scheduling while atomic:
rc.sysinit/1376/0x00000002
https://bugzilla.kernel.org/show_bug.cgi?id=22302
Theodore Tso <tytso@....edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tytso@....edu
--- Comment #1 from Theodore Tso <tytso@....edu> 2010-11-07 22:25:01 ---
This is caused by an interaction in two changes that happened in parallel in
2.6.36: commit id's dd3932eddf4 (block: remove BLKDEV_IFL_WAIT) and
commit 5c521830cf3 (ext4: Support discard requests when running in no-journal
mode).
The problem is that ext4_free_blocks() can be called by functions which are
holding spinlocks, so it can't sleep --- and sb_issue_discard() now always
waits for the discard to be completed. It doesn't support an asynchronous mode
at all.
The fix for the short-term is to remove the call to ext4_issue_discard() in
ext4_free_blocks(). This effectively removes the functionality of commit
5c521830cf3. The long-term fix would be to implement a version of
sb_issue_discard() which supports asynchronous mode, with an optional callback.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
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