linux-kernel - Re: [PATCH] quota: Turn quotas off when remounting read-only

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 11 Feb 2008 13:39:27 +0100
From:	Jan Kara <jack@...e.cz>
To:	Michael Tokarev <mjt@....msk.ru>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, stable@...nel.org
Subject: Re: [PATCH] quota: Turn quotas off when remounting read-only

On Thu 07-02-08 22:27:27, Michael Tokarev wrote:
> Andrew Morton wrote:
> > On Thu, 7 Feb 2008 15:37:21 +0100 Jan Kara <jack@...e.cz> wrote:
> > 
> >> Turn off quotas before filesystem is remounted read only. Otherwise quota will
> >> try to write to read-only filesystem which does no good... We could also just
> >> refuse to remount ro when quota is enabled but turning quota off is consistent
> >> with what we do on umount.
> 
> [a nice one-liner snipped]
> 
> > Cool.  And this is applicable to 2.6.23, 2.6.22 and even earlier, isn't it?
> 
> Provided the amount of time this issue exists, I don't think it's worth
> to push it to -stable.  It's an oooooooold, issue, which happens quite
> rarely, and no one bothered to report it so far...  But it's not my
> call... ;)
> 
> But...  I'm thinking about this scenario:
> 
>  # mount /data
>  # quotaon /data
>  (some maintenance stuff to be planned)
>  # mount -o remount,ro /data
>  (do backup etc)
>  # mount -r remount,rw /data
> 
> at this point, it's expected that quota on /data is enabled.
> After this patch, it's not anymore...
  Yes, it previously accidentally worked this way (for an year or so,
before that we refused to remount read-only). Hmm, but maybe we could
somehow tweak quotas to be turned on when remounting read-write again.
We have all the information we need at the time of remounting read-only
so we could store it and use it later when remounting read-write. I'll have
a look into that.

> I think it's more usual scenario than mine (umount instead of
> remount-rw).  And this change will break it.  So I'm not sure
> what really to do here.  Probably refusing remount-ro if quota
> is on is better...  it's annoying for sure, but at least it's
> explicit, and avoids the handg too.
  On the other hand when you umount the filesystem, quotas are
automatically turned off and when you mount it again, they are not enabled.
So the behavior as I've changed it is consistent as well... But probably
what I wrote above is the safest solution.

								Honza
-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/