public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Naman Jain <namjain@linux.microsoft.com>
To: Michael Kelley <mhklinux@outlook.com>,
	"K . Y . Srinivasan" <kys@microsoft.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: "linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Saurabh Sengar <ssengar@linux.microsoft.com>
Subject: Re: [PATCH 2/2] Drivers: hv: vmbus: Fix rescind handling in uio_hv_generic
Date: Mon, 26 Aug 2024 11:14:04 +0530	[thread overview]
Message-ID: <b179947f-a37f-41ff-8893-84e9eea42462@linux.microsoft.com> (raw)
In-Reply-To: <SN6PR02MB415711F672364610BBE6861DD48B2@SN6PR02MB4157.namprd02.prod.outlook.com>



On 8/26/2024 11:10 AM, Michael Kelley wrote:
> From: Naman Jain <namjain@linux.microsoft.com> Sent: Sunday, August 25, 2024 10:32 PM
>>
>> On 8/25/2024 8:27 AM, Michael Kelley wrote:
>>> From: Naman Jain <namjain@linux.microsoft.com> Sent: Thursday, August 22, 2024 4:09 AM
>>>>
>>>> Rescind offer handling relies on rescind callbacks for some of the
>>>> resources cleanup, if they are registered. It does not unregister
>>>> vmbus device for the primary channel closure, when callback is
>>>> registered.
>>>> Add logic to unregister vmbus for the primary channel in rescind callback
>>>> to ensure channel removal and relid release, and to ensure rescind flag
>>>> is false when driver probe happens again.
>>>>
>>>> Fixes: ca3cda6fcf1e ("uio_hv_generic: add rescind support")
>>>> Signed-off-by: Naman Jain <namjain@linux.microsoft.com>
>>>> ---
>>>>    drivers/hv/vmbus_drv.c       | 1 +
>>>>    drivers/uio/uio_hv_generic.c | 7 +++++++
>>>>    2 files changed, 8 insertions(+)
>>>>
>>>> diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
>>>> index c857dc3975be..4bae382a3eb4 100644
>>>> --- a/drivers/hv/vmbus_drv.c
>>>> +++ b/drivers/hv/vmbus_drv.c
>>>> @@ -1952,6 +1952,7 @@ void vmbus_device_unregister(struct hv_device *device_obj)
>>>>    	 */
>>>>    	device_unregister(&device_obj->device);
>>>>    }
>>>> +EXPORT_SYMBOL_GPL(vmbus_device_unregister);
>>>>
>>>>    #ifdef CONFIG_ACPI
>>>>    /*
>>>> diff --git a/drivers/uio/uio_hv_generic.c b/drivers/uio/uio_hv_generic.c
>>>> index c99890c16d29..ea26c0b460d6 100644
>>>> --- a/drivers/uio/uio_hv_generic.c
>>>> +++ b/drivers/uio/uio_hv_generic.c
>>>> @@ -121,6 +121,13 @@ static void hv_uio_rescind(struct vmbus_channel *channel)
>>>>
>>>>    	/* Wake up reader */
>>>>    	uio_event_notify(&pdata->info);
>>>> +
>>>> +	/*
>>>> +	 * With rescind callback registered, rescind path will not unregister the device
>>>> +	 * when the primary channel is rescinded. Without it, next onoffer msg does not come.
>>>> +	 */
>>>> +	if (!channel->primary_channel)
>>>> +		vmbus_device_unregister(channel->device_obj);
>>>
>>> When the rescind callback is *not* set, vmbus_onoffer_rescind() makes the
>>> call to vmbus_device_unregister(). But it does so bracketed with get_device()/
>>> put_device(). Your code here does not do the bracketing. Is there a reason for
>>> the difference? Frankly, I'm not sure why vmbus_onoffer_rescind() does the
>>> bracketing, and I can't definitively say if it is really needed. So I guess I'm
>>> just asking if you know. :-)
>>>
>>> Michael
>>
>> IMHO, we have already NULL checked channel->device_obj and other couple
>> of things to make sure we are safe to clean this up. At other places as
>> well, I don't see the use of put and get device. So I think its not
>> required. I am open to suggestions.
>>
>> Regards,
>> Naman
> 
> OK. I'm good with what you've said, and don't have any further suggestions.
> Go with what your patch already has. :-)
> 
> Michael

Thank you Michael. I'll wait for some time before posting v2, if there 
are any more review comments.

Regards,
Naman

  reply	other threads:[~2024-08-26  5:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-22 11:09 [PATCH 0/2] Drivers: vmbus: Fix rescind handling in uio_hv_generic Naman Jain
2024-08-22 11:09 ` [PATCH 1/2] uio_hv_generic: Fix kernel NULL pointer dereference in hv_uio_rescind Naman Jain
2024-08-24  3:09   ` Greg Kroah-Hartman
2024-08-25  2:51   ` Michael Kelley
2024-08-26  5:31     ` Naman Jain
2024-08-22 11:09 ` [PATCH 2/2] Drivers: hv: vmbus: Fix rescind handling in uio_hv_generic Naman Jain
2024-08-24  3:09   ` Greg Kroah-Hartman
2024-08-25  2:57   ` Michael Kelley
2024-08-26  5:31     ` Naman Jain
2024-08-26  5:40       ` Michael Kelley
2024-08-26  5:44         ` Naman Jain [this message]
2024-08-27 18:24         ` Saurabh Singh Sengar
2024-08-28 14:53           ` Michael Kelley

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=b179947f-a37f-41ff-8893-84e9eea42462@linux.microsoft.com \
    --to=namjain@linux.microsoft.com \
    --cc=decui@microsoft.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=haiyangz@microsoft.com \
    --cc=kys@microsoft.com \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhklinux@outlook.com \
    --cc=ssengar@linux.microsoft.com \
    --cc=stephen@networkplumber.org \
    --cc=wei.liu@kernel.org \
    /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