public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Simon Holm Thøgersen" <odie@cs.aau.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.29-rc1
Date: Mon, 12 Jan 2009 23:05:53 +0100	[thread overview]
Message-ID: <1231797954.2797.11.camel@odie.local> (raw)
In-Reply-To: <alpine.LFD.2.00.0901101551420.6528@localhost.localdomain>

lør, 10 01 2009 kl. 16:13 -0800, skrev Linus Torvalds:
> The merge window is over, and while it is quite possible that I missed a 
> few merge requests in the crazy week that is behind us, apart from those 
> we should now have most of the bulk of 2.6.29 merged up. And now it's just 
> a small matter of making sure it's all stable and ready to go.
> 
> I wanted to release -rc1 with time enough that by the time I'm on my way 
> to LCA next weekend, we'd have an -rc2 too, and the worst fallout from 
> -rc1 would be fixed.

Linus and Jonathan,

would you be so kind to make some noise about the reiserfs issue that
exists between c1eaa26 and 2f1169e?

Booting a kernel in that window results in a semi-broken reiserfs file
system (can boot but not build a new kernel etc.) and a fsck is needed
for complete restoration of consistency of fs. See also the original
report of the problem [1].

2.6.29-rc1 has the fix, but people like me that are doing bisections in
the 2.6.28..2.6.29-rc1 window are likely to run into the problem, and
should run something like the following after each git bisect bad/good

git rev-list HEAD | grep -q c1eaa26 && \
  (git rev-list HEAD | grep -q 2f1169e || git cherry-pick -n 2f1169e)

[1] http://marc.info/?l=linux-kernel&m=123106871227339&w=2


Simon Holm Thøgersen


  parent reply	other threads:[~2009-01-12 22:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-11  0:13 Linux 2.6.29-rc1 Linus Torvalds
2009-01-11  8:04 ` Willy Tarreau
2009-01-11 10:18 ` Paul Rolland
2009-01-11 12:07   ` David Miller
2009-01-11 12:23 ` Petr Titera
2009-01-11 13:23   ` Jaswinder Singh Rajput
2009-01-11 13:54   ` Ingo Molnar
2009-01-11 14:56     ` Petr Titera
2009-01-11 17:29 ` Gene Heskett
2009-01-11 17:55 ` Paul Rolland
2009-01-11 18:03   ` Ingo Molnar
2009-01-11 19:46     ` Paul Rolland
2009-01-11 20:10 ` Linux 2.6.29-rc1 MAJOR advisory Gene Heskett
2009-01-11 21:06   ` Torsten Kaiser
2009-01-12  2:50     ` Gene Heskett
2009-01-12  6:57       ` Torsten Kaiser
2009-01-12  7:15         ` Justin P. Mattock
2009-01-11 21:28 ` Linux 2.6.29-rc1 Maciej Rutecki
2009-01-11 21:35   ` Jesper Juhl
2009-01-11 21:38     ` Maciej Rutecki
2009-01-12 22:05 ` Simon Holm Thøgersen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-01-11 16:40 Torsten Schmidt
2009-01-11 18:19 ` Ingo Molnar

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=1231797954.2797.11.camel@odie.local \
    --to=odie@cs.aau.dk \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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