LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: shaggy@linux.vnet.ibm.com
To: torvalds@linux-foundation.org
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] jfs update
Date: Tue, 16 Jun 2009 14:14:10 -0500 (CDT)	[thread overview]
Message-ID: <20090616191410.D14714CA49E@norville.austin.ibm.com> (raw)

Linus, please pull from

git://git.kernel.org/pub/scm/linux/kernel/git/shaggy/jfs-2.6.git for-linus

This fixes a regression introduced in 2.6.30.  I'll send it to stable as well.

This will update the following files:

 fs/jfs/jfs_extent.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

through these ChangeSets:

commit f7c52fd17a7dda42fc9e88c2b2678403419bfe63
Author: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Date:   Tue Jun 16 13:43:22 2009 -0500

    jfs: fix regression preventing coalescing of extents
    
    Commit fec1878fe952b994125a3be7c94b1322db586f3b caused a regression in
    which contiguous blocks being allocated to the end of an extent were
    getting a new extent created.  This typically results in files entirely
    made up of 1-block extents even though the blocks are contiguous on
    disk.
    
    Apparently grub doesn't handle a jfs file being fragmented into too many
    extents, since it refuses to boot a kernel from jfs that was created by
    the 2.6.30 kernel.
    
    Signed-off-by: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
    Reported-by: Alex <alevkovich@tut.by>

             reply	other threads:[~2009-06-16 19:14 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16 19:14 shaggy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-07-27 14:55 Dave Kleikamp
2010-04-21 12:42 shaggy
2009-07-23 18:27 shaggy
2009-06-11 16:58 shaggy
2009-03-25 12:43 [git pull] " shaggy
2008-12-29 16:01 shaggy
2008-07-14 16:48 shaggy
2008-04-17 18:36 shaggy
2008-02-07 21:02 shaggy
2008-01-25 19:27 shaggy
2007-10-10 13:35 shaggy
2007-07-09 19:34 Dave Kleikamp
2007-05-08 14:51 Dave Kleikamp
2007-04-28 13:20 Dave Kleikamp
2007-02-14 23:08 Dave Kleikamp
2007-02-07 13:35 Dave Kleikamp
2006-12-12 15:16 Dave Kleikamp
2006-11-04  3:07 Dave Kleikamp
2006-11-02 14:23 Dave Kleikamp
2006-10-23 12:53 Dave Kleikamp
2006-10-02 15:16 Dave Kleikamp
2006-10-02 15:31 ` Linus Torvalds
2006-10-02 15:41   ` Dave Kleikamp
2006-10-02 16:21     ` Al Viro
2006-09-25 13:04 Dave Kleikamp
2006-08-03 14:37 Dave Kleikamp
2006-07-14  1:45 Dave Kleikamp
2006-07-06 14:20 Dave Kleikamp
2006-05-24 13:10 Dave Kleikamp
2006-03-20 14:57 Dave Kleikamp
2006-03-14 18:47 Dave Kleikamp
2006-03-14 19:33 ` Linus Torvalds
2005-11-09 21:40 Dave Kleikamp
2005-10-28 19:12 Dave Kleikamp
2005-08-04 21:07 Dave Kleikamp
2005-07-27 18:05 Dave Kleikamp
2005-07-27 23:43 ` Linus Torvalds
2005-07-13 14:41 Dave Kleikamp
2005-06-20 16:18 Dave Kleikamp
2005-05-04 20:47 Dave Kleikamp
2005-05-04 21:37 ` Linus Torvalds
2005-05-05 18:16   ` Jeff Garzik
2005-05-05 18:22     ` Linus Torvalds
2005-05-05 18:51       ` Dave Kleikamp
2005-05-05 19:39         ` Andrew Morton
2005-05-06 19:13           ` Dave Kleikamp

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=20090616191410.D14714CA49E@norville.austin.ibm.com \
    --to=shaggy@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: [GIT PULL] jfs update' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).