From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 59801] kernel BUG at /kernel/fs/ext4/extents.c:1996!
Date: Mon, 17 Jun 2013 12:35:29 +0000 (UTC) [thread overview]
Message-ID: <20130617123529.DEE8911FB51@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-59801-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=59801
Theodore Tso <tytso@mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |PATCH_ALREADY_AVAILABLE
--- Comment #4 from Theodore Tso <tytso@mit.edu> 2013-06-17 12:35:29 ---
Especially with ARM, where in general there is no standardization on C library
shared library bindings, etc., you really need to build user packages for
yourself. There are more modern (1.42.5) packages for e2fsprogs compiled for
ARM from Debian, but there's no guarantee that it will work on whatever system
you are using.
Please note that support of old kernels, especially kernels as old as 3.0, is
on "best effort" basis. People who have to use old kernels on a commercial
basis should get help from a commercial support organization (or build up ext4
expertise within their own organization, but the former is generally more
economically effective). There are a huge number of bug fixes since 3.0, and
while there are a few people will try to backport fixes to the 3.0 kernel, the
testing to make sure those fixes do not introduce new bugs, and the effort to
backport patches if they do not apply cleanly to older kernels, is very much on
a best effort basis.
If the problem is really obvious, as in this case, where I can find the problem
after looking for a few seconds, the open source community can try to give you
support. But if it requires more work than that, we can't help you --- we just
wouldn't have the time to improve ext4 for the upstream kernel if we were to
supply free support for ancient kernels. (Not to mention that it would not be
fair for those engineers whose salaries come from getting paid to support
ancient kernels.)
--
Configure bugmail: https://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:[~2013-06-17 12:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 2:20 [Bug 59801] New: kernel BUG at /kernel/fs/ext4/extents.c:1996! bugzilla-daemon
2013-06-17 2:22 ` [Bug 59801] " bugzilla-daemon
2013-06-17 3:22 ` bugzilla-daemon
2013-06-17 5:32 ` bugzilla-daemon
2013-06-17 12:35 ` bugzilla-daemon [this message]
2013-06-18 1:14 ` 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=20130617123529.DEE8911FB51@bugzilla.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).