From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12478] Infinite loop printing "__find_get_block_slow() failed." on accessing intentionally corrupted ext4 fs
Date: Tue, 19 May 2009 18:32:08 GMT [thread overview]
Message-ID: <200905191832.n4JIW8r2017216@demeter.kernel.org> (raw)
In-Reply-To: <bug-12478-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=12478
Theodore Tso <tytso@mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tytso@mit.edu
Regression|--- |No
--- Comment #3 from Theodore Tso <tytso@mit.edu> 2009-05-19 18:32:06 ---
This problem has been solved as of 2.6.30-rc1, when we added sanity checks when
initially fetching an inode, and when performing ext4_get_blocks()
logical->physical mappings.
--
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:[~2009-05-19 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 17:09 [Bug 12478] New: Infinite loop printing "__find_get_block_slow() failed." on accessing intentionally corrupted ext4 fs bugme-daemon
2009-01-18 17:10 ` [Bug 12478] " bugme-daemon
2009-01-18 17:14 ` bugme-daemon
2009-05-19 18:32 ` bugzilla-daemon [this message]
2009-05-19 18:32 ` bugzilla-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=200905191832.n4JIW8r2017216@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).