From: Wei Liu <wei.liu@kernel.org>
To: Dexuan Cui <decui@microsoft.com>
Cc: Mohammed Gamal <mgamal@redhat.com>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Michael Kelley (LINUX)" <mikelley@microsoft.com>,
"parri.andrea@gmail.com" <parri.andrea@gmail.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
"wei.liu@kernel.org" <wei.liu@kernel.org>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
"xxiong@redhat.com" <xxiong@redhat.com>
Subject: Re: [PATCH v3] Drivers: vmbus: Check for channel allocation before looking up relids
Date: Mon, 20 Feb 2023 14:23:50 +0000 [thread overview]
Message-ID: <Y/OCdpnGndMo8DCG@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <SA1PR21MB1335BBA8DF84AFDDF2E1ABE6BFA19@SA1PR21MB1335.namprd21.prod.outlook.com>
On Fri, Feb 17, 2023 at 11:17:04PM +0000, Dexuan Cui wrote:
> > From: Mohammed Gamal <mgamal@redhat.com>
> > Sent: Friday, February 17, 2023 12:44 PM
> > ...
> > --- a/drivers/hv/connection.c
> > +++ b/drivers/hv/connection.c
> > @@ -409,6 +409,10 @@ void vmbus_disconnect(void)
> > */
> > struct vmbus_channel *relid2channel(u32 relid)
> > {
> > + if (vmbus_connection.channels == NULL) {
> > + pr_warn_once("relid2channel: relid=%d: No channels mapped!\n",
> > relid);
>
> Looks good to me except that the line exceeds 80 characters.
> Please run "scripts/checkpatch.pl" to detect that.
> For this patch, I guess Wei may be willing to help fix it.
>
> > + return NULL;
> > + }
> > if (WARN_ON(relid >= MAX_CHANNEL_RELIDS))
> > return NULL;
> > return READ_ONCE(vmbus_connection.channels[relid]);
> > --
>
> Reviewed-by: Dexuan Cui <decui@microsoft.com>
I will pick this up via hyperv-fixes.
next prev parent reply other threads:[~2023-02-20 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 20:44 [PATCH v3] Drivers: vmbus: Check for channel allocation before looking up relids Mohammed Gamal
2023-02-17 23:17 ` Dexuan Cui
2023-02-20 11:39 ` Wei Liu
2023-02-20 14:23 ` Wei Liu [this message]
2023-03-06 15:28 ` Wei Liu
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=Y/OCdpnGndMo8DCG@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgamal@redhat.com \
--cc=mikelley@microsoft.com \
--cc=parri.andrea@gmail.com \
--cc=vkuznets@redhat.com \
--cc=xxiong@redhat.com \
/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.