This still seems lacking a definite feedback. The supposed fix is in the
proposed kernel package which can be also found via the following link
https://launchpad.net/ubuntu/jaunty/+source/linux/2.6.28-15.48 (then
following the links to the builds to the right). It would be great if
someone could
This bug was fixed in the package linux - 2.6.28-15.48
---
linux (2.6.28-15.48) jaunty-proposed; urgency=low
[ Andy Whitcroft ]
* SAUCE: pnp: add PNP resource range checking function
- LP: #349314
* SAUCE: i915: enable MCHBAR if needed
- LP: #349314
[ Brad Figg ]
Could someone please /finish/ the documentation in
https://wiki.ubuntu.com/Testing/EnableProposed? The blurb in italics
asking how to actually accomplish more than seeing a package list has
been there for ages, and that's about as far as I can get as well.
Aptitude does nothing because it
Accepted linux into jaunty-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
As these locking issues often are sensitive to timing, it could well be
that other changes had some influence. The problem with the stable
kernels is that, after the experience with 2.6.27.y which received a
huge amount of updates and sometimes caused regressions, we now went
back to cherry-pick
According to http://lkml.org/lkml/2009/4/30/545, there will not be any
more 2.6.28 stable releases. However, there have been three 2.6.27
releases since then, the latest of which includes this patch along with
a bunch of other ext4 patches. Would it be worthwhile to ask upstream
(Greg KH?) to
This should be resolved for Karmic but I'm opening a Jaunty nomination
for the kernel team to consider a stable release update for Jaunty.
** Changed in: linux (Ubuntu)
Status: New = Fix Released
** Also affects: linux (Ubuntu Jaunty)
Importance: Undecided
Status: New
**
I guess he means that one...
http://git.kernel.org/?p=linux/kernel/git/tytso/ext4.git;a=commitdiff;h=16cb5dd9f53e569130584696909d423b6fe38c1e
--
[PATCH] ext4 filesystem corruption
https://bugs.launchpad.net/bugs/389555
You received this bug notification because you are a member of Ubuntu
Bugs,
Oops, wrong task
** Description changed:
+
+ SRU Justification:
+
+ Impact: As mentioned by Ted Tso (see link below) there has been a data
+ corruption issue fixed in ext4 after 2.6.28.y was stopped.
+
+ Fix: A cherry pick from upstream from Ted's repo.
+
+ Testcase: unfortunately not
