[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <DM5PR2101MB091836C94C52C1B3469C5380D7420@DM5PR2101MB0918.namprd21.prod.outlook.com>
Date: Thu, 21 Mar 2019 15:55:22 +0000
From: Michael Kelley <mikelley@...rosoft.com>
To: Sasha Levin <sashal@...nel.org>, kimbrownkd <kimbrownkd@...il.com>
CC: Long Li <longli@...rosoft.com>,
Sasha Levin <Alexander.Levin@...rosoft.com>,
Stephen Hemminger <sthemmin@...rosoft.com>,
Dexuan Cui <decui@...rosoft.com>,
Greg KH <gregkh@...uxfoundation.org>,
KY Srinivasan <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
"linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v6] Drivers: hv: vmbus: Expose monitor data only when
monitor pages are used
From: Sasha Levin <sashal@...nel.org> Sent: Wednesday, March 20, 2019 8:57 PM
>
> I've queued it up for hyperv-fixes, thanks Kimberly.
>
> Should this go in stable as well?
>
My take: these changes lean more toward being a "clean up" rather
than fixing a problem that has significant impact. The data in the sysfs
entries is bogus, but isn't actually hurting anything. The current code does
index off the end of an array in some cases, but the accesses are reads
and there's plenty of padding so that actually making an invalid memory
reference won't happen. In the interest of reducing churn in the
stable branches, I would lean toward *not* backporting this to stable.
Michael
Powered by blists - more mailing lists