From: Dexuan Cui <decui@microsoft.com>
To: David Miller <davem@davemloft.net>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"driverdev-devel@linuxdriverproject.org"
<driverdev-devel@linuxdriverproject.org>,
"olaf@aepfle.de" <olaf@aepfle.de>,
"apw@canonical.com" <apw@canonical.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
KY Srinivasan <kys@microsoft.com>,
"pebolle@tiscali.nl" <pebolle@tiscali.nl>
Subject: RE: [V2 6/7] hvsock: introduce Hyper-V VM Sockets feature
Date: Thu, 16 Jul 2015 11:19:01 +0000 [thread overview]
Message-ID: <d1e303ece500475b8e422d55f82fbffd@SIXPR30MB031.064d.mgd.msft.net> (raw)
In-Reply-To: <20150715.211916.1258342954251964451.davem@davemloft.net>
> From: David Miller
> Sent: Thursday, July 16, 2015 12:19
>
> From: Dexuan Cui
> Date: Tue, 14 Jul 2015 03:00:48 -0700
>
> > + pr_debug("hvsock_sk_destruct: called\n");
>
> Debug logging just to state that a function is called is not appropriate,
> we have very sophisticated tracing facilities in the kernel that can do
> that transparently, and more.
>
> Please remove this.
OK.
> > + if (hvsk->channel) {
> > + pr_debug("hvsock_sk_destruct: calling vmbus_close()\n");
>
> Likewise, these kinds of debug logs are totally inappropriate.
OK, I'll remove all the pr_debug() in the patch.
> > +static int hvsock_release(struct socket *sock)
> > +{
> > + /* sock->sk is NULL, if accept() is interrupted by a signal */
> > + if (sock->sk) {
> > + __hvsock_release(sock->sk);
> > + sock->sk = NULL;
> > + }
> > +
> > + sock->state = SS_FREE;
> > + pr_debug("hvsock_release called\n\n");
>
> Likewise.
OK. Will fix it.
Thanks,
-- Dexuan
next prev parent reply other threads:[~2015-07-16 11:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 10:00 Dexuan Cui
2015-07-16 4:19 ` David Miller
2015-07-16 11:19 ` Dexuan Cui [this message]
2015-07-17 15:04 ` Vitaly Kuznetsov
2015-07-20 5:30 ` Dexuan Cui
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=d1e303ece500475b8e422d55f82fbffd@SIXPR30MB031.064d.mgd.msft.net \
--to=decui@microsoft.com \
--cc=apw@canonical.com \
--cc=davem@davemloft.net \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=pebolle@tiscali.nl \
--cc=stephen@networkplumber.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
all inboxes | Powered by JetHome®