linux-hyperv.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Naman Jain <namjain@linux.microsoft.com>
To: Dexuan Cui <decui@microsoft.com>,
	KY Srinivasan <kys@microsoft.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Wei Liu <wei.liu@kernel.org>,
	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>,
	"stable@kernel.org" <stable@kernel.org>,
	Saurabh Sengar <ssengar@linux.microsoft.com>,
	Michael Kelley <mhklinux@outlook.com>
Subject: Re: [PATCH v5 1/2] uio_hv_generic: Fix sysfs creation path for ring buffer
Date: Tue, 22 Apr 2025 19:55:45 +0530	[thread overview]
Message-ID: <54905359-035b-4974-bdae-3e60e903adbd@linux.microsoft.com> (raw)
In-Reply-To: <BL4PR21MB4627D99C78C22A8C3355059CBFBF2@BL4PR21MB4627.namprd21.prod.outlook.com>



On 4/18/2025 6:39 AM, Dexuan Cui wrote:
>> From: Naman Jain <namjain@linux.microsoft.com>
>> Sent: Tuesday, April 15, 2025 9:45 AM
>> Subject: [PATCH v5 1/2] uio_hv_generic: Fix sysfs creation path for ring buffer
>>
>> On regular bootup, devices get registered to VMBus first, so when
>> uio_hv_generic driver for a particular device type is probed,
>> the device is already initialized and added, so sysfs creation in
>> uio_hv_generic probe works fine. However, when device is removed
> 
> Sorry, I'd like to nitpick :-) I guess the maintainer(s) can fix these for you
> so v6 might not be necessary, if there is no comment from others.
> 
> s/uio_hv_generic probe/hv_uio_probe()/
> s/device/the device/
> 
>> and brought back, the channel rescinds and device again gets
> s/rescinds and device/gets rescinded and the device/
> 
>> registered to VMBus. However this time, the uio_hv_generic driver is
>> already registered to probe for that device and in this case sysfs
>> creation is tried before the device's kobject gets initialized
>> completely.
>>
>> Fix this by moving the core logic of sysfs creation for ring buffer,
> s/for/of/
> 
>> from uio_hv_generic to HyperV's VMBus driver, where rest of the sysfs
> s/rest/the rest/
> 
>> attributes for the channels are defined. While doing that, make use
>> of attribute groups and macros, instead of creating sysfs directly,
>> to ensure better error handling and code flow.
>>
>> Problem path:
> s/Problem/Problematic/
> 
>> vmbus_process_offer (new offer comes for the VMBus device)
> s/new/A new/
> 
>>    vmbus_add_channel_work
>>      vmbus_device_register
>>        |-> device_register
>>        |     |...
>>        |     |-> hv_uio_probe
>>        |           |...
>>        |           |-> sysfs_create_bin_file (leads to a warning as
>>        |                 primary channel's kobject, which is used to
> s/primary/the primary/
> 
>>        |                 create sysfs is not yet initialized)
> s/sysfs/the sysfs file, /
> 
>>        |-> kset_create_and_add
>>        |-> vmbus_add_channel_kobj (initialization of primary channel's
> s/primary/the primary/
> 
>>                                    kobject happens later)
>>
> 
> Reviewed-by: Dexuan Cui <decui@microsoft.com>


Thanks Dexuan. I'll make the required changes and send next patch.

Regards,
Naman


  reply	other threads:[~2025-04-22 14:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 16:44 [PATCH v5 0/2] uio_hv_generic: Fix ring buffer sysfs creation path Naman Jain
2025-04-15 16:44 ` [PATCH v5 1/2] uio_hv_generic: Fix sysfs creation path for ring buffer Naman Jain
2025-04-18  1:09   ` Dexuan Cui
2025-04-22 14:25     ` Naman Jain [this message]
2025-04-15 16:44 ` [PATCH v5 2/2] Drivers: hv: Make the sysfs node size for the ring buffer dynamic Naman Jain
2025-04-18  1:13   ` Dexuan Cui
2025-04-22 14:26     ` Naman Jain

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=54905359-035b-4974-bdae-3e60e903adbd@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=stable@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).