[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <SA1PR21MB13357D76B8D865DA58F19EE4BF239@SA1PR21MB1335.namprd21.prod.outlook.com>
Date: Tue, 11 Oct 2022 23:27:05 +0000
From: Dexuan Cui <decui@...rosoft.com>
To: Cezar Bulinaru <cbulinaru@...il.com>,
KY Srinivasan <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
"wei.liu@...nel.org" <wei.liu@...nel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"edumazet@...gle.com" <edumazet@...gle.com>,
"kuba@...nel.org" <kuba@...nel.org>,
"linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [PATCH] net: hyperv: bugcheck trigered by memcpy in rndis_filter
> From: Cezar Bulinaru <cbulinaru@...il.com>
> Sent: Tuesday, October 11, 2022 12:26 PM
> Subject: [PATCH] net: hyperv: bugcheck trigered by memcpy in rndis_filter
A better subject line is:
[PATCH] hv_netvsc: Fix a warning triggered by memcpy in rndis_filter
(please refer to "git log drivers/net/hyperv/rndis_filter.c", and there was
a typo in your subject: s/trigered/triggered )
> A bugcheck is trigered when the response message len exceeds
s/bugcheck/warning
I think a bugcheck is a crash in Windows's terminology.
Here it's just a harmless warning rather than a crash.
Powered by blists - more mailing lists