linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jan Kara <jack@suse.cz>, LKML <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PULL REQUEST] Ext2, ext3, and quota updates for 2.6.35-rc1
Date: Fri, 21 May 2010 21:24:56 +0200	[thread overview]
Message-ID: <20100521192456.GE10149@quack.suse.cz> (raw)
In-Reply-To: <alpine.LFD.2.00.1005211146160.3689@i5.linux-foundation.org>

On Fri 21-05-10 11:50:15, Linus Torvalds wrote:
> 
> 
> On Fri, 21 May 2010, Jan Kara wrote:
> >
> >   Oops, I've just found a bug in one of my ocfs2 fixes. I've fixed that up
> > so the new diffstat is here:
> 
> I already pulled your previous version.
  OK, I'll push the fix separately.

> And btw, Jan, I'm getting pretty upset with your apparently cavalier 
> attitude to filesystems. We've had several bugs lately for some quota or 
> filesystem "cleanups", which in at least one case caused corrupted 
> filesystems etc.
  That ext3 bug was nasty I agree :( I'm now pushing some quota tests to
XFSQA and setup a machine that runs them. So that should improve a test
coverage...

> You need to be a hell of a lot more careful, or I will have to stop 
> pulling from you. Filesystem bugs are _major_ no-no's. 
> 
> How long had that buggy commit been tested? By who? Was it acked or 
> reviewed by anybody else?
  The buggy commit was "ocfs2: Fix lock inversion in quotas during umount"
and it was reviewed by Joel Becker. Neither of us realized that we have to
stop quota syncing thread also on remount read-only...

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  reply	other threads:[~2010-05-21 19:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-21 17:46 [PULL REQUEST] Ext2, ext3, and quota updates for 2.6.35-rc1 Jan Kara
2010-05-21 18:44 ` Jan Kara
2010-05-21 18:50   ` Linus Torvalds
2010-05-21 19:24     ` Jan Kara [this message]
2010-05-22  0:05       ` Dave Chinner

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=20100521192456.GE10149@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).