From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 11688] Oops while writing on a newly ext4 formated 1TB partition on a external USB drive
Date: Tue, 20 Jan 2009 09:18:43 -0800 (PST) [thread overview]
Message-ID: <20090120171843.787B410800C@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-11688-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=11688
------- Comment #9 from jack@suse.cz 2009-01-20 09:18 -------
Ted, I've looked into this and it is a bug in ext4. It should call
grab_cache_page_write_begin() with AOP_FLAG_NOFS since it cannot handle
recursion into the filesystem for freeing memory. The problem is that at the
time grab_cache_page_write_begin() is called, a transaction is already started
- this is what quota code complains about (because it also needs to start a
transaction but current->journal_info is already occupied by ext4).
If we wanted to avoid AOP_FLAG_NOFS we could get the page, start a transaction,
lock and check the page but that's going to be a bit nasty.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2009-01-20 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11688-13602@http.bugzilla.kernel.org/>
2008-11-06 20:27 ` [Bug 11688] Oops while writing on a newly ext4 formated 1TB partition on a external USB drive bugme-daemon
2009-01-18 0:24 ` bugme-daemon
2009-01-18 23:39 ` bugme-daemon
2009-01-19 0:56 ` bugme-daemon
2009-01-19 1:18 ` bugme-daemon
2009-01-19 2:28 ` bugme-daemon
2009-01-19 8:50 ` bugme-daemon
2009-01-20 17:18 ` bugme-daemon [this message]
2009-02-05 16:30 ` bugme-daemon
2009-02-24 16:22 ` bugme-daemon
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=20090120171843.787B410800C@picon.linux-foundation.org \
--to=bugme-daemon@bugzilla.kernel.org \
--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).