From: lkml@dhtns.com
To: linux-kernel@vger.kernel.org
Cc: lkml@dhtns.com
Subject: JFS resize=0 problem in 2.6.0
Date: Sun, 28 Dec 2003 10:30:28 -0500 [thread overview]
Message-ID: <20031228153028.GB22247@faraday.dhtns.com> (raw)
Let me know if I'm missing the goal of the code here, but lines 261-273
of linux-2.6.0/fs/jfs/super.c are:
case Opt_resize:
{
char *resize = args[0].from;
if (!resize || !*resize) { /* LINE 264 HERE */
*newLVSize = sb->s_bdev->bd_inode->i_size >>
sb->s_blocksize_bits;
if (*newLVSize == 0)
printk(KERN_ERR
"JFS: Cannot determine volume size\n");
} else
*newLVSize = simple_strtoull(resize, &resize, 0);
break;
}
It seems to me that line 264 is attempting to test for the mount
paramater "resize=0", and when it comes across this, resize to the full
size of the volume. However, this doesn't work. I believe it should
test for the char '0' (*resize=='0'), not against literal zero.
Let me know if I'm way off base here. But the below patch does allow a
$ mount -o remount,resize=0 /mnt/test
to resize the jfs filesystem to the full size of the volume.
Ok, I've never submitted a patch before, but here goes:
--- linux-2.6.0/fs/jfs/super.c 2003-12-28 10:16:00.000000000 -0500
+++ linux/fs/jfs/super.c 2003-12-28 10:15:34.000000000 -0500
@@ -261,7 +261,7 @@
case Opt_resize:
{
char *resize = args[0].from;
- if (!resize || !*resize) {
+ if (!resize || !*resize || *resize=='0') {
*newLVSize = sb->s_bdev->bd_inode->i_size >>
sb->s_blocksize_bits;
if (*newLVSize == 0)
-Elliott Bennett
lkml@dhtns.com
next reply other threads:[~2003-12-28 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-28 15:30 lkml [this message]
2003-12-29 0:05 ` JFS resize=0 problem in 2.6.0 Mike Fedyk
2004-01-02 20:12 ` Elliott Bennett
2004-01-02 21:24 ` Mike Fedyk
2004-01-02 22:28 ` Christophe Saout
2004-01-02 22:33 ` Christophe Saout
2004-01-06 15:24 ` Elliott Bennett
2004-01-05 17:07 ` Dave Kleikamp
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=20031228153028.GB22247@faraday.dhtns.com \
--to=lkml@dhtns.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.