All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: lkml <linux-kernel@vger.kernel.org>,
	"ext3-users@redhat.com" <ext3-users@redhat.com>
Subject: ext3 0.9.13 for linux 2.4.13-pre6
Date: Sun, 21 Oct 2001 18:21:03 -0700	[thread overview]
Message-ID: <3BD3747F.6893E49D@zip.com.au> (raw)

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.

                 reply	other threads:[~2001-10-22  1:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3BD3747F.6893E49D@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=ext3-users@redhat.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.