[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <SA1PR21MB1335D6E10CF9043EA74573F7BFA19@SA1PR21MB1335.namprd21.prod.outlook.com>
Date: Fri, 17 Feb 2023 19:00:08 +0000
From: Dexuan Cui <decui@...rosoft.com>
To: Vitaly Kuznetsov <vkuznets@...hat.com>,
Mohammed Gamal <mgamal@...hat.com>,
"linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Michael Kelley (LINUX)" <mikelley@...rosoft.com>,
"parri.andrea@...il.com" <parri.andrea@...il.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
"wei.liu@...nel.org" <wei.liu@...nel.org>,
"xxiong@...hat.com" <xxiong@...hat.com>
Subject: RE: [PATCH v2] Drivers: vmbus: Check for channel allocation before
looking up relids
> From: Vitaly Kuznetsov <vkuznets@...hat.com>
> Sent: Friday, February 17, 2023 1:52 AM
>
> I'd even suggest to make it pr_warn_once() to be
> safe. In theory, vmbus_chan_sched() call site looks like it can create a
> lot of noise.
Good point.
Powered by blists - more mailing lists