[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <KL1P15301MB000651716C4B0DBAE6DD99FBBF370@KL1P15301MB0006.APCP153.PROD.OUTLOOK.COM>
Date: Mon, 11 Dec 2017 20:41:44 +0000
From: Dexuan Cui <decui@...rosoft.com>
To: Stephen Hemminger <stephen@...workplumber.org>,
Greg KH <gregkh@...uxfoundation.org>
CC: "olaf@...fle.de" <olaf@...fle.de>,
Stephen Hemminger <sthemmin@...rosoft.com>,
"jasowang@...hat.com" <jasowang@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
"apw@...onical.com" <apw@...onical.com>,
"marcelo.cerri@...onical.com" <marcelo.cerri@...onical.com>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"vkuznets@...hat.com" <vkuznets@...hat.com>,
"leann.ogasawara@...onical.com" <leann.ogasawara@...onical.com>
Subject: RE: [PATCH 1/2] vmbus: unregister device_obj->channels_kset
> From: devel [mailto:driverdev-devel-bounces@...uxdriverproject.org] On
> Behalf Of Stephen Hemminger
> Sent: Tuesday, November 28, 2017 9:30 AM
> To: Greg KH <gregkh@...uxfoundation.org>
> Cc: olaf@...fle.de; Stephen Hemminger <sthemmin@...rosoft.com>;
> jasowang@...hat.com; linux-kernel@...r.kernel.org; stable@...r.kernel.org;
> apw@...onical.com; marcelo.cerri@...onical.com;
> devel@...uxdriverproject.org; vkuznets@...hat.com;
> leann.ogasawara@...onical.com
> Subject: Re: [PATCH 1/2] vmbus: unregister device_obj->channels_kset
>
> On Tue, 28 Nov 2017 16:56:05 +0100
> Greg KH <gregkh@...uxfoundation.org> wrote:
>
> > On Tue, Nov 14, 2017 at 06:53:32AM -0700, kys@...hange.microsoft.com
> wrote:
> > > From: Dexuan Cui <decui@...rosoft.com>
> > >
> > > Fixes: c2e5df616e1a ("vmbus: add per-channel sysfs info")
> > >
> > > Without the patch, a device can't be thoroughly destroyed, because
> > > vmbus_device_register() -> kset_create_and_add() still holds a reference
> > > to the hv_device's device.kobj.
> > >
> > > Signed-off-by: Dexuan Cui <decui@...rosoft.com>
> > > Cc: Stephen Hemminger <sthemmin@...rosoft.com>
> > > Cc: stable@...r.kernel.org
> >
> > Why is this marked for stable when the patch it "fixes" is in 4.15-rc1?
>
> It doesn't need to go to stable.
Hi Greg,
May I know the status of the patch?
Thanks,
-- Dexuan
Powered by blists - more mailing lists