From: KY Srinivasan <kys@microsoft.com>
To: Olaf Hering <olaf@aepfle.de>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 1/2] tools: hv: use FIFREEZE/FITHAW in hv_vss_daemon
Date: Tue, 26 Mar 2013 18:43:15 +0000 [thread overview]
Message-ID: <d5b20c7b60cd48a6a78e541f42493b87@SN2PR03MB061.namprd03.prod.outlook.com> (raw)
In-Reply-To: <1364316430-29655-1-git-send-email-olaf@aepfle.de>
> -----Original Message-----
> From: Olaf Hering [mailto:olaf@aepfle.de]
> Sent: Tuesday, March 26, 2013 12:47 PM
> To: KY Srinivasan; gregkh@linuxfoundation.org
> Cc: linux-kernel@vger.kernel.org; Olaf Hering
> Subject: [PATCH 1/2] tools: hv: use FIFREEZE/FITHAW in hv_vss_daemon
>
> As suggested by Paolo Bonzini, use ioctl instead of calling fsfreeze.
>
> Signed-off-by: Olaf Hering <olaf@aepfle.de>
Thanks Olaf for taking care of this.
Acked by: K. Y. Srinivasan <kys@microsoft.com>
> ---
>
> NOT runtime tested!!
>
> tools/hv/hv_vss_daemon.c | 31 ++++++++++++++++++++++---------
> 1 file changed, 22 insertions(+), 9 deletions(-)
>
> diff --git a/tools/hv/hv_vss_daemon.c b/tools/hv/hv_vss_daemon.c
> index e37d86c..830d606 100644
> --- a/tools/hv/hv_vss_daemon.c
> +++ b/tools/hv/hv_vss_daemon.c
> @@ -21,7 +21,9 @@
> #include <sys/types.h>
> #include <sys/socket.h>
> #include <sys/poll.h>
> +#include <sys/ioctl.h>
> #include <linux/types.h>
> +#include <fcntl.h>
> #include <stdio.h>
> #include <mntent.h>
> #include <stdlib.h>
> @@ -30,6 +32,7 @@
> #include <ctype.h>
> #include <errno.h>
> #include <arpa/inet.h>
> +#include <linux/fs.h>
> #include <linux/connector.h>
> #include <linux/hyperv.h>
> #include <linux/netlink.h>
> @@ -44,21 +47,35 @@ static struct sockaddr_nl addr;
> #endif
>
>
> +static int vss_do_freeze(char *dir, unsigned int cmd, char *fs_op)
> +{
> + int ret, fd = open(dir, O_RDONLY);
> +
> + if (fd < 0)
> + return 1;
> + ret = ioctl(fd, cmd, 0);
> + syslog(LOG_INFO, "VSS: %s of %s: %s\n", fs_op, dir, strerror(errno));
> + close(fd);
> + return !!ret;
> +}
> +
> static int vss_operate(int operation)
> {
> char *fs_op;
> - char cmd[512];
> char match[] = "/dev/";
> FILE *mounts;
> struct mntent *ent;
> + unsigned int cmd;
> int error = 0, root_seen = 0;
>
> switch (operation) {
> case VSS_OP_FREEZE:
> - fs_op = "-f ";
> + cmd = FIFREEZE;
> + fs_op = "freeze";
> break;
> case VSS_OP_THAW:
> - fs_op = "-u ";
> + cmd = FITHAW;
> + fs_op = "thaw";
> break;
> default:
> return -1;
> @@ -75,16 +92,12 @@ static int vss_operate(int operation)
> root_seen = 1;
> continue;
> }
> - snprintf(cmd, sizeof(cmd), "fsfreeze %s '%s'", fs_op, ent-
> >mnt_dir);
> - syslog(LOG_INFO, "VSS cmd is %s\n", cmd);
> - error |= system(cmd);
> + error |= vss_do_freeze(ent->mnt_dir, cmd, fs_op);
> }
> endmntent(mounts);
>
> if (root_seen) {
> - sprintf(cmd, "fsfreeze %s /", fs_op);
> - syslog(LOG_INFO, "VSS cmd is %s\n", cmd);
> - error |= system(cmd);
> + error |= vss_do_freeze("/", cmd, fs_op);
> }
>
> return error;
>
prev parent reply other threads:[~2013-03-26 18:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 16:47 Olaf Hering
2013-03-26 16:47 ` [PATCH 2/2] tools: hv: skip iso9660 mounts " Olaf Hering
2013-03-26 18:44 ` KY Srinivasan
2013-03-26 18:43 ` KY Srinivasan [this message]
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=d5b20c7b60cd48a6a78e541f42493b87@SN2PR03MB061.namprd03.prod.outlook.com \
--to=kys@microsoft.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
/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
all inboxes | Powered by JetHome®