public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Avantika Mathur LTC <mathur@us.ibm.com>
To: linux-ext4@vger.kernel.org
Subject: ext4 devel interlock meeting minutes (Sept. 20, 2006)
Date: Wed, 20 Sep 2006 10:03:51 -0700	[thread overview]
Message-ID: <45117477.1030000@us.ibm.com> (raw)

Ext4 Developer Interlock Call: 9/20/06 Minutes

Attendees: Shaggy (Dave Kleikamp), Jean-Pierre Dion, Alexandre Ratchov, 
Valérie Clément, Eric Sandeen, Avantika Mathur

- Shaggy has ported the patch set to 2.6.18-rc7-mm1, and will post the 
patches today.  Some of the patches are redundant and should be merged 
together, Shaggy and Alexandre will be working on this.  These patches 
have only been compile tested, and need more thorough testing.  
Alexandre has been running ext4 on a 20 TB sparse disk for a month and 
has not encountered any problems.

- Shaggy and Alexandre will also look back at all of the comments on the 
original post, to verify they have been addressed in the updated series.

- Now that 2.6.18 is up, We assume Andrew Morton will be pushing current 
ext3 patches in the -mm tree to 2.6.19-rc1.  At that point we will try 
to merge ext4 patches.

- Alexandre is waiting for feedback from Ted on e2fsprogs patches.  Plan 
to discuss and review through the mailing list.

- A bug in the JBD patches was found last week; JBD and JBD2 use the 
same slab. The kernel crashes if ext3 and ext4 are both loaded. This 
problem is probably still present in current set. Easily reproduced by 
loading ext3 and ext4 modules, the second one will crash because of 
duplicate slab name.

-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2006-09-20 17:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-20 17:03 Avantika Mathur LTC [this message]
2006-09-21 12:48 ` ext4 devel interlock meeting minutes (Sept. 20, 2006) Theodore Tso

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=45117477.1030000@us.ibm.com \
    --to=mathur@us.ibm.com \
    --cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox