From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jan Kara <jack@suse.cz>, LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, dushistov@mail.ru,
joel.becker@oracle.com, shaggy@linux.vnet.ibm.com,
linux-ext4@vger.kernel.org
Subject: Re: [PULL REQUEST] Quota cleanups & fixes and ext3 fixes for 2.6.34-rc1
Date: Fri, 5 Mar 2010 23:01:17 +0000 [thread overview]
Message-ID: <20100305230117.GZ30031@ZenIV.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.00.1003051314330.3906@localhost.localdomain>
On Fri, Mar 05, 2010 at 01:24:35PM -0800, Linus Torvalds wrote:
>
>
> On Fri, 5 Mar 2010, Jan Kara wrote:
> >
> > could you please pull from
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs-2.6.git for_linus
> >
> > You'll get lots of quota cleanups from Christoph which touch filesystems
> > all over the place but it's just function renaming and moving quota calls
> > from VFS into filesystems themselves.
>
> Gaah. This interacted with the VFS stuff (the do_filp_open() cleanip in
> particular) I merged from Al earlier today.
>
> It really looked very trivial, so I fixed it up. Al had split up
> do_filp_open() into several helper functions, and one of your changes was
> to the old pre-split one. I felt confident enough about it that I just did
> the obvious merge resolution, but you guys should check it out to be sure.
It's OK as merge resolution, but I really wonder if that patch (taking
quota initialization to filesystems) is a good idea. It adds boilerplate
code that is easy to miss. And looking at what's done in e.g. ext2,
I'd say that places where it's added are lousy - if we want to do that
on directory modifications, we ought to take it into places that actually
create directory entries. Not to mention that we never shrink directories
there, so it should be just one call in ext2_add_link() instead of all
that pile.
Looks like a good case for a followup series, if nothing else.
prev parent reply other threads:[~2010-03-05 23:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 0:33 [PULL REQUEST] Quota cleanups & fixes and ext3 fixes for 2.6.34-rc1 Jan Kara
2010-03-05 21:24 ` Linus Torvalds
2010-03-05 23:01 ` Al Viro [this message]
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=20100305230117.GZ30031@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=dushistov@mail.ru \
--cc=jack@suse.cz \
--cc=joel.becker@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@linux.vnet.ibm.com \
--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).