From: "David S. Miller" <davem@davemloft.net>
To: Richard Mortimer <richm@oldelvet.org.uk>, marcelo.tosatti@cyclades.com
Cc: sparclinux@vger.kernel.org, linux-lvm@sistina.com,
debian-sparc@lists.debian.org
Subject: [linux-lvm] [PATCH] Re: lvm problems on sparc64 - Trying to vfree() nonexistent vm area
Date: Mon, 30 Aug 2004 17:40:15 -0700 [thread overview]
Message-ID: <20040830174015.10edb69b.davem@davemloft.net> (raw)
In-Reply-To: <1093911340.2116.55.camel@duncow>
On Tue, 31 Aug 2004 01:15:40 +0100
Richard Mortimer <richm@oldelvet.org.uk> wrote:
> I'm seeing problems with lvm on sparc64. I have a reproducible test case
> using snapshots where I can reliably reproduce an error similar to
>
> Trying to vfree() nonexistent vm area (0000000140072000)
For once it's not sparc64's fault, it's a bug in the generic
LVM ioctl handling :-)
It saves both pointers, clobbers the userspace copy, then only
restores one of the two pointers correctly. Easy to fix, see
below.
Marcelo, please apply, thanks.
# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
# 2004/08/30 17:24:05-07:00 davem@nuts.davemloft.net
# [LVM]: Do not forget to restore both user pointers.
#
# This in particular can make compatability layers
# crash, and it is a bug for regular applications
# too.
#
# Signed-off-by: David S. Miller <davem@davemloft.net>
#
# drivers/md/lvm.c
# 2004/08/30 17:23:48-07:00 davem@nuts.davemloft.net +12 -0
# [LVM]: Do not forget to restore both user pointers.
#
# This in particular can make compatability layers
# crash, and it is a bug for regular applications
# too.
#
# Signed-off-by: David S. Miller <davem@davemloft.net>
#
diff -Nru a/drivers/md/lvm.c b/drivers/md/lvm.c
--- a/drivers/md/lvm.c 2004-08-30 17:24:13 -07:00
+++ b/drivers/md/lvm.c 2004-08-30 17:24:13 -07:00
@@ -2689,6 +2689,10 @@
(&lv_status_byname_req.lv->lv_current_pe,
&saved_ptr1, sizeof(void *)) != 0)
return -EFAULT;
+ if (copy_to_user
+ (&lv_status_byname_req.lv->lv_block_exception,
+ &saved_ptr2, sizeof(void *)) != 0)
+ return -EFAULT;
return 0;
}
}
@@ -2743,6 +2747,10 @@
(&lv_status_byindex_req.lv->lv_current_pe, &saved_ptr1,
sizeof(void *)) != 0)
return -EFAULT;
+ if (copy_to_user
+ (&lv_status_byindex_req.lv->lv_block_exception, &saved_ptr2,
+ sizeof(void *)) != 0)
+ return -EFAULT;
return 0;
} /* lvm_do_lv_status_byindex() */
@@ -2799,6 +2807,10 @@
/* Restore usermode pointers */
if (copy_to_user
(&lv_status_bydev_req.lv->lv_current_pe, &saved_ptr1,
+ sizeof(void *)) != 0)
+ return -EFAULT;
+ if (copy_to_user
+ (&lv_status_bydev_req.lv->lv_block_exception, &saved_ptr2,
sizeof(void *)) != 0)
return -EFAULT;
next prev parent reply other threads:[~2004-08-31 0:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 0:15 [linux-lvm] lvm problems on sparc64 - Trying to vfree() nonexistent vm area Richard Mortimer
2004-08-31 0:40 ` David S. Miller [this message]
2004-08-31 22:00 ` [linux-lvm] Re: [PATCH] " Richard Mortimer
2004-09-02 1:37 ` David S. Miller
2004-09-02 10:58 ` Richard Mortimer
2004-09-02 20:28 ` David S. Miller
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=20040830174015.10edb69b.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=debian-sparc@lists.debian.org \
--cc=linux-lvm@redhat.com \
--cc=linux-lvm@sistina.com \
--cc=marcelo.tosatti@cyclades.com \
--cc=richm@oldelvet.org.uk \
--cc=sparclinux@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