On Mon, Mar 18, 2002 at 05:45:27PM +0100, Dave Jones wrote:
> On Mon, Mar 18, 2002 at 08:42:15AM -0800, Mike Fedyk wrote:
> > Dave, can you put kernel versions next to the problem reports?
> > That way it'll be easier to see just how old the report is and see if it
> > should be tested again (for testers) or fixed (for developers).
> At the top. "Up to date as of 2.5.6pre1."
> (Yes, I'm a the report is a whole 4 patches behind..
> I'll fix it up maybe later tonight)
2. Capable Of Corrupting Your FS/data.
* Some reports of unknown cause of ext2 corruption since 2.5.3 (not
related to the missing i_fsize clearing from .3pre3-5)
It would be good to report the last version that this problem was reported
against, and this type of problem can't really be tested on each pre patch.
That's basically what I was asking for before...
# IDE floppy oops on some (zip100) setups. (Triggers BUG_ON() in
If the version is reported for this then you can see what function was being
reported at the time. Otherwise some other patch could shift the contents
to make line 237 point to another function (rewrites and such...)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Mar 23 2002 - 22:00:15 EST