From: Olaf Hering <olaf@aepfle.de>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, apw@canonical.com,
jasowang@redhat.com
Subject: Re: [PATCH V3 1/1] Drivers: hv: Implement the file copy service
Date: Tue, 21 Jan 2014 20:13:26 +0100 [thread overview]
Message-ID: <20140121191326.GA16171@aepfle.de> (raw)
In-Reply-To: <1390331164-14292-1-git-send-email-kys@microsoft.com>
On Tue, Jan 21, K. Y. Srinivasan wrote:
Looks better. A few comments below:
> +++ b/drivers/hv/hv_fcopy.c
> +static bool daemon_died;
This is a write only variable.
> +static u32 daemon_version;
This is a write only variable.
> +static int fcopy_handle_handshake(u32 version)
> +{
> + pr_info("FCP: user-mode registering done. Daemon version: %d\n",
> + version);
> + fcopy_transaction.active = false;
> + daemon_version = version;
I think fcopy_handle_handshake should proactivly reject requests if
version is not 0.
There is an unused FCOPY_VERSION as well. I think this should not be in
a header. Instead the kernel should handle all known versions and reject
everything it does not know about.
> + syslog(LOG_INFO, "Target file name: %s\n", target_fname);
Newline in syslog
> + if (mkdir((char *)smsg->path_name, 0755)) {
> + syslog(LOG_ERR, "Failed to create %s\n",
Newline in syslog
> + syslog(LOG_INFO, "File: %s exists\n", target_fname);
Newline in syslog
> + syslog(LOG_INFO, "Open Failed: %s\n", strerror(errno));
Newline in syslog
> + syslog(LOG_ERR, "Read error: %s\n",
Newline in syslog
> + syslog(LOG_ERR, "Unknown operation: %d\n",
Newline in syslog
Olaf
prev parent reply other threads:[~2014-01-21 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 19:06 [PATCH V3 1/1] Drivers: hv: Implement the file copy service K. Y. Srinivasan
2014-01-21 19:01 ` Levente Kurusa
2014-01-21 19:09 ` KY Srinivasan
2014-01-21 19:13 ` Olaf Hering [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=20140121191326.GA16171@aepfle.de \
--to=olaf@aepfle.de \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox