| 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
| ||
|
Date: Wed, 19 Mar 2008 10:54:42 +0100 From: Jan Kara <jack@...e.cz> To: Jan Engelhardt <jengelh@...putergmbh.de> Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org Subject: Re: [PATCH] Do not allow setting of quota limits to too high values On Tue 18-03-08 22:48:49, Jan Engelhardt wrote: > > On Mar 18 2008 17:44, Jan Kara wrote: >>>>> >>>>> For 2.6.26, I assume? I am not able to determine the seriousness of >>>>> this >>>>> problem from the changelog nor from the patch itself. >>>> >>>> Not really serious. Nobody complained so far (i.e., for the time quota >>>> exists) and the limits will just wrap when you try to set them over 4TB >>>> now. So the patch can wait... >>> So does quota_v2.c even handle quotas > 4 TB? >> Usage yes, limits no. But some Sun guys are already working on a patch >> for fully 64-bit quota. I already have a decent kernel patch from him but >> I'd like to see also tools support to really run it before merging the >> patch :). > > Does this also affect XFS? No. All XFS quotas have in common with VFS quotas is the name of the syscall (quotactl()). All the rest is different and XFS has everywhere 64-bit fields. 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/
Powered by blists - more mailing lists