From: Stephen Hemminger <stephen@networkplumber.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: kys@microsoft.com, olaf@aepfle.de, sthemmin@microsoft.com,
jasowang@redhat.com, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, marcelo.cerri@canonical.com,
apw@canonical.com, devel@linuxdriverproject.org,
vkuznets@redhat.com, leann.ogasawara@canonical.com
Subject: Re: [PATCH 1/2] vmbus: unregister device_obj->channels_kset
Date: Tue, 28 Nov 2017 09:29:40 -0800 [thread overview]
Message-ID: <20171128092940.0cec2377@xeon-e3> (raw)
In-Reply-To: <20171128155605.GA19015@kroah.com>
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.
next prev parent reply other threads:[~2017-11-28 17:29 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 [this message]
2017-12-11 20:41 ` Dexuan Cui
2017-12-11 20:58 ` Greg KH
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=20171128092940.0cec2377@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.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=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).