From: Greg KH <gregkh@suse.de>
To: "Ozan Çağlayan" <ozan@pardus.org.tr>
Cc: Thomas Voegtle <tv@lio96.de>, Jan Kara <jack@suse.cz>,
"Theodore Ts'o" <tytso@mit.edu>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@kernel.org,
dmonakhov@openvz.org
Subject: Re: Linux 2.6.31.10
Date: Wed, 13 Jan 2010 13:45:16 -0800 [thread overview]
Message-ID: <20100113214516.GC11701@suse.de> (raw)
In-Reply-To: <4B4E387B.2050900@pardus.org.tr>
On Wed, Jan 13, 2010 at 11:17:47PM +0200, Ozan Çağlayan wrote:
> Ozan Çağlayan wrote:
>
> > This causes kernel panic upon boot on one of our users' ext3 system (on 2.6.31.11) so I think 2.6.30.y deserves another
> > stable update to fix this critical issue.
>
> oops, 2.6.30.y should be 2.6.31.y, sorry.
Yes, .31 will be getting another release with this fix in it, sorry for
the delay, been stuck debugging other things these past few days...
thanks,
greg k-h
next prev parent reply other threads:[~2010-01-13 21:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 23:45 Linux 2.6.31.10 Greg KH
2010-01-06 23:45 ` Greg KH
2010-01-07 14:27 ` Thomas Voegtle
2010-01-07 18:04 ` Greg KH
2010-01-07 19:36 ` Thomas Voegtle
2010-01-07 19:41 ` Greg KH
2010-01-07 20:33 ` Thomas Voegtle
2010-01-07 20:42 ` Thomas Voegtle
2010-01-07 22:02 ` Greg KH
2010-01-08 0:03 ` Dmitry Monakhov
2010-01-08 0:53 ` [PATCH] quota: fix reserved space management for ordinary fs Dmitry Monakhov
2010-01-08 11:03 ` Thomas Voegtle
2010-01-08 12:24 ` Teck Choon Giam
2010-01-08 12:41 ` Jan Kara
2010-01-08 15:52 ` Greg KH
2010-01-12 12:23 ` Jan Kara
2010-01-12 14:24 ` Greg KH
2010-01-08 12:39 ` Linux 2.6.31.10 Jan Kara
2010-01-13 21:15 ` Ozan Çağlayan
2010-01-13 21:17 ` Ozan Çağlayan
2010-01-13 21:45 ` Greg KH [this message]
2010-01-07 18:12 ` Teck Choon Giam
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=20100113214516.GC11701@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=dmonakhov@openvz.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=ozan@pardus.org.tr \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tv@lio96.de \
--cc=tytso@mit.edu \
/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