From: Thomas Voegtle <tv@lio96.de>
To: Greg KH <gregkh@suse.de>
Cc: 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: Thu, 7 Jan 2010 21:33:29 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.00.1001072125040.26784@er-systems.de> (raw)
In-Reply-To: <20100107194131.GA22983@suse.de>
On Thu, 7 Jan 2010, Greg KH wrote:
> On Thu, Jan 07, 2010 at 08:36:07PM +0100, Thomas Voegtle wrote:
>> On Thu, 7 Jan 2010, Greg KH wrote:
>>
>>> On Thu, Jan 07, 2010 at 03:27:21PM +0100, Thomas Voegtle wrote:
>>>> Hi,
>>>>
>>>> On Wed, 6 Jan 2010, Greg KH wrote:
>>>>> I'm announcing the release of the 2.6.31.10 kernel. All users of the
>>>>> 2.6.31 kernel series are very strongly encouraged to upgrade.
>>>>
>>>>
>>>> Something broken here, during using a suse 11.2 installation with quota
>>>> switched on (this is reproducible )
>>>
>>> Jan, this looks like something in the quota patches you sent. Any
>>> ideas?
>>>
>>> Thomas, is this on an ext3 or ext4 partition, or something else?
>>
>>
>> The one with quota enabled was an ext3 partition, mounted on /
>
> Thanks.
>
> Could you run 'git bisect' between the two kernel versions to try to
> track the problem down to the single patch?
Done, between 2.6.31.9 and 2.6.31.11
c169e13a6662cbf36fc0098508e7aa31b49cbf23 is first bad commit
commit c169e13a6662cbf36fc0098508e7aa31b49cbf23
Author: Dmitry Monakhov <dmonakhov@openvz.org>
Date: Mon Dec 14 15:21:13 2009 +0300
quota: decouple fs reserved space from quota reservation
commit fd8fbfc1709822bd94247c5b2ab15a5f5041e103 upstream.
Reverting that patch on top of 2.6.31.11 fixes the problem for me.
next prev parent reply other threads:[~2010-01-07 20:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 23:45 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 [this message]
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
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=alpine.LNX.2.00.1001072125040.26784@er-systems.de \
--to=tv@lio96.de \
--cc=akpm@linux-foundation.org \
--cc=dmonakhov@openvz.org \
--cc=gregkh@suse.de \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
--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
all inboxes | Powered by JetHome®