From: Christoph Hellwig <hch@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org,
Nathan Scott <nathans@wobbly.melbourne.sgi.com>
Subject: Re: Quota patches
Date: Mon, 20 May 2002 15:07:57 +0100 [thread overview]
Message-ID: <20020520150757.A16965@infradead.org> (raw)
In-Reply-To: <20020520135530.GB9209@atrey.karlin.mff.cuni.cz>
On Mon, May 20, 2002 at 03:55:31PM +0200, Jan Kara wrote:
> quota-2.5.15-3-register - this patch implements registering/unregistering of quota
> formats
Please don't use the big kernel lock for a newly added list.
Also using <linux/lists.h> would clean up the list handling.
> quota-2.5.15-4-getstats - this patch removes Q_GETSTATS call and creates /proc/fs/quota
> entry instead
Yuck, even more /proc abuse. Please convert it to the seq_file interface
at least. Using individual sysctls per value would be much better.
> quota-2.5.15-7-quotactl - implementation of generic quotactl interface (probably the
> biggest patch). Interface is moved from dquot.c to quota.c file. Pointers
> to quota operations in superblock are now not filled on quota_on() but
> on mount so filesystem can override them (for example ext3 would like to
> check on quota_on() that quotafile lies on proper device and turn on
> data-journaling on it - at least when we'll have journaled quota :)).
The vfs_get*/vfs_set* names sound too generic, could you please rename them
to vfs_get_quota*/vfs_set_quota*?
Also I think any quota supporting filesystem should set the quota operations
explicitly to make the intention clearer.
> quota-2.5.15-12-compat - implements backward compatible quotactl() interface. It's
> configurable whether it should be used at all and whether is should behave
> as interface in Linus's (the oldest interface) or Alan's (old interface for
> new quota format) kernel.
I don't think we want to keep old userspace interface in 2.5, it just
bloats the kernel and requiring quota tools for a development kernel that
are already required by all vendor kernels sounds sane to me.
Else your patches look very good to me, I look forward to finally see
properly working quota support in a mainline kernel.
Christoph
next prev parent reply other threads:[~2002-05-20 14:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-20 13:55 Quota patches Jan Kara
2002-05-20 14:07 ` Christoph Hellwig [this message]
2002-05-20 15:38 ` Jan Kara
2002-05-22 19:46 ` OGAWA Hirofumi
2002-05-22 19:57 ` Jan Kara
2002-05-22 23:30 ` Nathan Scott
2002-05-23 0:59 ` Nathan Scott
2002-05-23 1:56 ` Alan Cox
2002-05-23 1:55 ` Nathan Scott
2002-05-23 9:16 ` Jan Kara
2002-05-23 17:03 ` Linus Torvalds
2002-05-24 2:35 ` Nathan Scott
2002-05-24 3:46 ` Linus Torvalds
2002-05-24 14:58 ` Jan Kara
2002-05-24 14:10 ` Martin Dalecki
2002-05-24 15:43 ` Alan Cox
2002-05-24 14:31 ` Martin Dalecki
2002-05-24 15:43 ` Christoph Hellwig
2002-05-24 14:43 ` Martin Dalecki
2002-05-24 16:12 ` Alan Cox
2002-05-24 15:55 ` Christoph Hellwig
2002-05-24 14:54 ` Martin Dalecki
2002-05-24 16:18 ` Alan Cox
2002-05-24 16:14 ` Alan Cox
2002-05-24 16:01 ` David Woodhouse
2002-05-24 18:41 ` Thunder from the hill
2002-05-24 15:07 ` Alan Cox
[not found] <20020523154249.X180298@wobbly.melbourne.sgi.com>
2002-05-23 8:53 ` Jan Kara
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=20020520150757.A16965@infradead.org \
--to=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@wobbly.melbourne.sgi.com \
--cc=torvalds@transmeta.com \
/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