From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 15025] Oops in ext4 driver
Date: Wed, 17 Feb 2010 13:48:11 GMT [thread overview]
Message-ID: <201002171348.o1HDmBTW031193@demeter.kernel.org> (raw)
In-Reply-To: <bug-15025-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=15025
--- Comment #11 from Dmitry Monakhov <dmonakhov@openvz.org> 2010-02-17 13:47:27 ---
After the patch i can not trigger the bug (In reply to comment #10)
> On Tue, Feb 16, 2010 at 02:08:33PM +0000, bugzilla-daemon@bugzilla.kernel.org
> wrote:
> > The issue was fixed by following commit
> > http://git.kernel.org/?p=linux/kernel/git/tytso/ext4.git;a=commit;h=1db913823c0f8360fccbd24ca67eb073966a5ffd
>
> This cannot be, as I don't use quota.
It i is posible to triger the bug without quota.
Untill the patch it we have following code
fs/ext4/inode.c:
1850 if (ext4_claim_free_blocks(sbi, md_needed + 1)) {
1851 vfs_dq_release_reservation_block(inode, md_needed + 1);
1852 if (ext4_should_retry_alloc(inode->i_sb, &retries)) {
1853 retry:
1854 if (md_reserved)
1855 write_inode_now(inode, (retries == 3));
^^^^^^^^^^ Here we goes in to lack of journal credits. ^^^^^^^^^^^^^^^^^^^^^^
1856 yield();
1857 goto repeat;
1858 }
1859 return -ENOSPC;
1860 }
You have failed exactly here.
So the bug happens even in case of ENOSPC (try following testase):
dd if=/dev/zero /mnt/BIG_FILE bs=1M
But it takes longer if partition is really huge.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2010-02-17 13:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 13:09 [Bug 15025] New: Oops in ext4 driver bugzilla-daemon
2010-01-13 22:09 ` [Bug 15025] " bugzilla-daemon
2010-01-13 22:16 ` bugzilla-daemon
2010-01-24 23:07 ` bugzilla-daemon
2010-01-27 19:35 ` bugzilla-daemon
2010-01-27 20:23 ` bugzilla-daemon
2010-02-16 13:44 ` bugzilla-daemon
2010-02-16 14:08 ` bugzilla-daemon
2010-02-16 21:00 ` bugzilla-daemon
2010-02-16 21:00 ` bugzilla-daemon
2010-02-16 23:57 ` bugzilla-daemon
2010-02-17 0:21 ` bugzilla-daemon
2010-02-17 13:48 ` bugzilla-daemon [this message]
2010-02-17 13:51 ` bugzilla-daemon
[not found] <md-TZL3UUvL.A.FiE.xJMXLB@chimera>
[not found] ` <hE3x9c-4KZM.A.IRG.kKMXLB@chimera>
[not found] ` <20100124224330.GA2230@uio.no>
[not found] ` <20100124224330.GA2230-6Z/AllhyZU4@public.gmane.org>
2010-01-24 23:09 ` [Bug #15025] " Rafael J. Wysocki
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=201002171348.o1HDmBTW031193@demeter.kernel.org \
--to=bugzilla-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).