An ext3 patch for the latest Linus kernel is at http://www.uow.edu.au/~andrewm/linux/ext3/ The changes are quite small: - Tided up some code now that quotas in Linus and -ac kernels are synced up. - Fix a race which can cause a null-pointer deref in ext3_writepage(). This bug has been there for a long time, but only manifested in 2.3.13-pre for some reason. I've tested this pretty hard, every which way. It looks OK. There was a report against ext3-for-2.4.10 that mark_buffer_clean() was being called against an already-clean buffer. This has not been reproducable (in later kernels, at least). If anyone sees the message "jbd_preclean_buffer_check: clean of clean buffer" come out, please shout. This can only happen if ext3 debugging support is enabled in config.
Hi, Is the official patch for linux 2.4.13-pre6 supposed to be stable or experimental or what? It seems odd releasing an official patch against an unofficial kernel. Does this just mean that problems with recent kernels have been solved and when the final kernel 2.4.13 comes out an ext3 patch will quickly follow? I'm confused. __________________________________________________________________ Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/ Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/
Is the official patch for linux 2.4.13-pre6 supposed to be stable or experimental or what? It seems odd releasing an official patch against an unofficial kernel. Does this just mean that problems with recent kernels have been solved and when 2.4.13 comes out an ext3 patch for it will quickly follow? I'm confused.
On Mon, 22 Oct 2001 10:14:18 -0700 Andrew Morton <akpm@zip.com.au> wrote:> Tim Tassonis wrote: > > > > Thanks a lot for the effort. > > > > - It applies without any problem > > - tune2fs seems to work (can add journal to mounted partition, can setmax> > mount count) > > Cool. > > > Hopefully the frequent "cannot read lock file /etc/mtab~" accompaniedby a> > /dev/null with no permissions are gone as well. > > > > hmm? I don't recall a report on this one. Maybe I was asleep. > What were the circumstances?Sorry, but I didn't report it, since I thought that was one of the problems with 2.4.10 that you already mentioned. If it ever appears again, I will provide you with a detailed report, of course. Bye Tim