linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: Christoph Hellwig <hch@infradead.org>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/6] dquot: move remount handling into the filesystem
Date: Wed, 19 May 2010 06:55:17 -0400	[thread overview]
Message-ID: <20100519105517.GA5106@infradead.org> (raw)
In-Reply-To: <20100517223418.GG3364@quack.suse.cz>

On Tue, May 18, 2010 at 12:34:18AM +0200, Jan Kara wrote:
>   It seems you have missed out UDF from the conversion (maybe you could
> setup a checklist of filesystem to convert? :) OTOH looking at it more in
> detail quota support for UDF is broken (i.e. quotaon returns EINVAL because
> .quota_write is not set) for several years now and noone has complained so
> I'm starting to wonder whether fixing it is worth the effort.

It's probably not worth it.  Given that quota is not part of the UDF
spec, and the linux quota formats are non-portable is's probably rather
worthless.  The same applies to UFS which has also beend disabled for
long.  Do you want me to send patches to remove UDF and UFS quota
support?

>   Also I'm slightly concerned that previous vfs_dq_quota_on_remount was
> called only after
>   sb->s_flags = (sb->s_flags & ~MS_RMT_MASK) | (flags & MS_RMT_MASK);
> so in particular MS_RDONLY has been cleared. Now it is called before so
> some filesystem could possibly barf when it sees writes from quota system
> before MS_RDONLY gets cleared. I've checked and only JFS could have this
> problem since others already clear MS_RDONLY inside their foo_remount()
> functions but still...

I've added explicit clears of MS_RDONLY to the next revision of the
patch in jfs and udf.

> >  		spin_unlock(&sbi->s_lock);
> > +
> >  		ext2_write_super(sb);
> > +		enable_quota = 1;
> >  	}
> > +
> > +	if (enable_quota)
> > +		vfs_dq_quota_on_remount(sb);
>   I kind of miss the purpose of "enable_quota" in the above...
> Also the ENOSYS check was there only for filesystems which do not support
> quotas. Since all the filesystems that call vfs_dq_off now obviously do
> support quotas, you can just drop it.

Indeed.  It was left over from an earlier version of the patch that had
locking constrainst that made it nessecary.  I've removed it for the
next version.


  reply	other threads:[~2010-05-19 10:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-12 19:44 [PATCH 0/6] more quota cleanups Christoph Hellwig
2010-05-12 19:44 ` [PATCH 1/6] dquot: move remount handling into the filesystem Christoph Hellwig
2010-05-17 22:34   ` Jan Kara
2010-05-19 10:55     ` Christoph Hellwig [this message]
2010-05-19 13:47       ` Jan Kara
2010-05-12 19:44 ` [PATCH 2/6] quota: kill the vfs_dq_off and vfs_dq_quota_on_remount wrappers Christoph Hellwig
2010-05-17 22:46   ` Jan Kara
2010-05-12 19:44 ` [PATCH 3/6] dquot: move unmount handling into the filesystem Christoph Hellwig
2010-05-17 22:58   ` Jan Kara
2010-05-19 11:03     ` Christoph Hellwig
2010-05-12 19:44 ` [PATCH 4/6] quota: drop remount argument to ->quota_on and ->quota_off Christoph Hellwig
2010-05-17 23:00   ` Jan Kara
2010-05-12 19:44 ` [PATCH 5/6] quota: explicitly set ->dq_op and ->s_qcop Christoph Hellwig
2010-05-17 23:06   ` Jan Kara
2010-05-19 11:07     ` Christoph Hellwig
2010-05-12 19:44 ` [PATCH 6/6] quota: rename default quotactl methods to dqout_ Christoph Hellwig
2010-05-17 23:09   ` Jan Kara
2010-05-19 11:07     ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2010-05-19 11:16 [PATCH 0/6] more quota cleanups V2 Christoph Hellwig
2010-05-19 11:16 ` [PATCH 1/6] dquot: move remount handling into the filesystem Christoph Hellwig

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=20100519105517.GA5106@infradead.org \
    --to=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.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).