From: Greg KH <gregkh@linuxfoundation.org>
To: Dexuan Cui <decui@microsoft.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
"olaf@aepfle.de" <olaf@aepfle.de>,
Stephen Hemminger <sthemmin@microsoft.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"apw@canonical.com" <apw@canonical.com>,
"marcelo.cerri@canonical.com" <marcelo.cerri@canonical.com>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
"leann.ogasawara@canonical.com" <leann.ogasawara@canonical.com>
Subject: Re: [PATCH 1/2] vmbus: unregister device_obj->channels_kset
Date: Mon, 11 Dec 2017 21:58:58 +0100 [thread overview]
Message-ID: <20171211205858.GA19427@kroah.com> (raw)
In-Reply-To: <KL1P15301MB000651716C4B0DBAE6DD99FBBF370@KL1P15301MB0006.APCP153.PROD.OUTLOOK.COM>
On Mon, Dec 11, 2017 at 08:41:44PM +0000, Dexuan Cui wrote:
> > From: devel [mailto:driverdev-devel-bounces@linuxdriverproject.org] On
> > Behalf Of Stephen Hemminger
> > Sent: Tuesday, November 28, 2017 9:30 AM
> > To: Greg KH <gregkh@linuxfoundation.org>
> > Cc: olaf@aepfle.de; Stephen Hemminger <sthemmin@microsoft.com>;
> > jasowang@redhat.com; linux-kernel@vger.kernel.org; stable@vger.kernel.org;
> > apw@canonical.com; marcelo.cerri@canonical.com;
> > devel@linuxdriverproject.org; vkuznets@redhat.com;
> > leann.ogasawara@canonical.com
> > Subject: Re: [PATCH 1/2] vmbus: unregister device_obj->channels_kset
> >
> > On Tue, 28 Nov 2017 16:56:05 +0100
> > Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > > On Tue, Nov 14, 2017 at 06:53:32AM -0700, kys@exchange.microsoft.com
> > wrote:
> > > > From: Dexuan Cui <decui@microsoft.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@microsoft.com>
> > > > Cc: Stephen Hemminger <sthemmin@microsoft.com>
> > > > Cc: stable@vger.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?
It's still in my "to-apply" queue. As it's only a 4.15-final thing,
don't worry, it will get there...
thanks,
greg k-h
next prev parent reply other threads:[~2017-12-11 20:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1510667553-2991-1-git-send-email-kys@exchange.microsoft.com>
2017-11-14 13:53 ` [PATCH 1/2] vmbus: unregister device_obj->channels_kset kys
2017-11-28 15:56 ` Greg KH
2017-11-28 17:29 ` Stephen Hemminger
2017-12-11 20:41 ` Dexuan Cui
2017-12-11 20:58 ` Greg KH [this message]
2017-12-11 21:02 ` Dexuan Cui
2017-11-14 13:53 ` [PATCH 2/2] Drivers: hv: vmbus: Fix a rescind issue kys
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=20171211205858.GA19427@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=apw@canonical.com \
--cc=decui@microsoft.com \
--cc=devel@linuxdriverproject.org \
--cc=jasowang@redhat.com \
--cc=leann.ogasawara@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.cerri@canonical.com \
--cc=olaf@aepfle.de \
--cc=stable@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.com \
--cc=vkuznets@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).