linux-ext4 - [Bug 59801] kernel BUG at /kernel/fs/ext4/extents.c:1996!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20130617123529.DEE8911FB51@bugzilla.kernel.org>
Date:	Mon, 17 Jun 2013 12:35:29 +0000 (UTC)
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 59801] kernel BUG at /kernel/fs/ext4/extents.c:1996!

https://bugzilla.kernel.org/show_bug.cgi?id=59801

Theodore Tso <tytso@....edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |PATCH_ALREADY_AVAILABLE

--- Comment #4 from Theodore Tso <tytso@....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.
--
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