From: Eric Sandeen <sandeen@redhat.com>
To: xfs-oss <xfs@oss.sgi.com>
Cc: James Lawrie <james@jdlawrie.co.uk>
Subject: [PATCH] xfsprogs: check for size parsing errors in xfs_quota
Date: Mon, 23 Jan 2012 11:31:53 -0600 [thread overview]
Message-ID: <4F1D9989.8060808@redhat.com> (raw)
Doing something like
# xfs_quota -x -c 'limit -u bhard=1.2g ...
will cause cvtnum to fail and return a value of -1LL (because it
cannot parse the decimal), but the quota caller doesn't check
for this error value, casts it to U64, shifts right, and we end
up with an answer of 16 petabytes rather than erroring out.
Fix this.
Reported-by: James Lawrie <james@jdlawrie.co.uk>
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
diff --git a/quota/edit.c b/quota/edit.c
index b704e63..067cd63 100644
--- a/quota/edit.c
+++ b/quota/edit.c
@@ -226,13 +226,17 @@ extractb(
uint sectorsize,
__uint64_t *value)
{
- __uint64_t v;
+ long long v;
char *s = string;
if (strncmp(string, prefix, length) == 0) {
s = string + length + 1;
- v = (__uint64_t)cvtnum(blocksize, sectorsize, s);
- *value = v >> 9; /* syscalls use basic blocks */
+ v = cvtnum(blocksize, sectorsize, s);
+ if (v == -1LL) {
+ fprintf(stderr, _("%s: Error: could not parse size %s.\n"), progname, s);
+ return 0;
+ }
+ *value = (__uint64_t)v >> 8; /* syscalls use basic blocks */
if (v > 0 && *value == 0)
fprintf(stderr, _("%s: Warning: `%s' in quota blocks is 0 (unlimited).\n"), progname, s);
return 1;
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-01-23 17:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 17:31 Eric Sandeen [this message]
2012-01-23 19:59 ` [PATCH] xfsprogs: check for size parsing errors in xfs_quota Christoph Hellwig
2012-01-24 5:07 ` Eric Sandeen
2012-01-24 17:56 ` Christoph Hellwig
2012-01-24 17:58 ` Eric Sandeen
2012-01-27 19:26 ` [PATCH V2] " Eric Sandeen
2012-02-03 17:41 ` Mark Tinguely
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=4F1D9989.8060808@redhat.com \
--to=sandeen@redhat.com \
--cc=james@jdlawrie.co.uk \
--cc=xfs@oss.sgi.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