From: Naman Jain <namjain@linux.microsoft.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "K . Y . Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>,
Stephen Hemminger <stephen@networkplumber.org>,
linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@kernel.org, Saurabh Sengar <ssengar@linux.microsoft.com>,
Michael Kelley <mhklinux@outlook.com>
Subject: Re: [PATCH v6 0/2] uio_hv_generic: Fix ring buffer sysfs creation path
Date: Fri, 2 May 2025 11:31:03 +0530 [thread overview]
Message-ID: <2173d71c-301d-4b6c-b839-0e747d0d0a4b@linux.microsoft.com> (raw)
In-Reply-To: <2025050154-skyward-snagged-973d@gregkh>
On 5/1/2025 9:35 PM, Greg Kroah-Hartman wrote:
> On Mon, Apr 28, 2025 at 02:37:22PM +0530, Naman Jain wrote:
>>
>>
>> On 4/25/2025 7:30 PM, Greg Kroah-Hartman wrote:
>>> On Thu, Apr 24, 2025 at 11:05:22AM +0530, Naman Jain wrote:
>>>> Hi,
>>>> This patch series aims to address the sysfs creation issue for the ring
>>>> buffer by reorganizing the code. Additionally, it updates the ring sysfs
>>>> size to accurately reflect the actual ring buffer size, rather than a
>>>> fixed static value.
>>>>
>>>> PFB change logs:
>>>>
>>>> Changes since v5:
>>>> https://lore.kernel.org/all/20250415164452.170239-1-namjain@linux.microsoft.com/
>>>> * Added Reviewed-By tags from Dexuan. Also, addressed minor comments in
>>>> commit msg of both patches.
>>>> * Missed to remove check for "primary_channel->device_obj->channels_kset" in
>>>> hv_create_ring_sysfs in earlier patch, as suggested by Michael. Did it
>>>> now.
>>>> * Changed type for declaring bin_attrs due to changes introduced by
>>>> commit 9bec944506fa ("sysfs: constify attribute_group::bin_attrs") which
>>>> merged recently. Did not use bin_attrs_new since another change is in
>>>> the queue to change usage of bin_attrs_new to bin_attrs
>>>> (sysfs: finalize the constification of 'struct bin_attribute').
>>>
>>> Please fix up to apply cleanly without build warnings:
>>>
>>> drivers/hv/vmbus_drv.c:1893:15: error: initializing 'struct bin_attribute **' with an expression of type 'const struct bin_attribute *const[2]' discards qualifiers in nested pointer types [-Werror,-Wincompatible-pointer-types-discards-qualifiers]
>>> 1893 | .bin_attrs = vmbus_chan_bin_attrs,
>>> | ^~~~~~~~~~~~~~~~~~~~
>>> 1 error generated.
>>
>> Hi Greg,
>> I tried reproducing this error but could not see it. Should I rebase the
>> change to some other tree or use some specific config option, gcc version,
>> compilation flag etc.?
>>
>> I tried the following:
>> * Rebased to latest linux-next tip with below base commit:
>> 393d0c54cae31317deaa9043320c5fd9454deabc
>> * Regular compilation with gcc: make -j8
>> * extra flags:
>> make -j8 EXTRA_CFLAGS="-Wall -O2"
>> make -j8 EXTRA_CFLAGS="-Wincompatible-pointer-types-discards-qualifiers
>> -Werror"
>> * Tried gcc 11.4, 13.3
>> * Tried clang/LLVM with version 18.1.3 : make LLVM=1
>
> I tried this against my char-misc-linus branch (which is pretty much
> just 6.15.0-rc4 plus some iio patches), and it fails with that error
> above.
>
>> BTW I had to edit the type for bin_attrs as this change got merged recently:
>> 9bec944506fa ("sysfs: constify attribute_group::bin_attrs")
>>
>> diff --git a/include/linux/sysfs.h b/include/linux/sysfs.h
>> index 576b8b3c60af..f418aae4f113 100644
>> --- a/include/linux/sysfs.h
>> +++ b/include/linux/sysfs.h
>> @@ -107,7 +107,7 @@ struct attribute_group {
>> int);
>> struct attribute **attrs;
>> union {
>> - struct bin_attribute **bin_attrs;
>> + const struct bin_attribute *const *bin_attrs;
>> const struct bin_attribute *const *bin_attrs_new;
>> };
>> };
>
> That commit is not in my char-misc branches, that's coming from
> somewhere else.
>
> thanks,
>
> greg k-h
Hi Greg,
I can send a patch based on char-misc/6.15.0-rc4 which does not have
this patch, but I am worried that it will cause compilation issues when
your branch is merged with linux-next since this change is already there
in linux-next. Do you want me to proceed with sending a patch on 6.15.0-rc4?
Here are more details of that patch:
"""
sysfs: constify attribute_group::bin_attrs
All users of this field have been migrated to bin_attrs_new.
It can now be constified.
Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
Link:
https://lore.kernel.org/r/20250313-sysfs-const-bin_attr-final-v2-2-96284e1e88ce@weissschuh.net
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
"""
Regards,
Naman
next prev parent reply other threads:[~2025-05-02 6:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 5:35 [PATCH v6 0/2] uio_hv_generic: Fix ring buffer sysfs creation path Naman Jain
2025-04-24 5:35 ` [PATCH v6 1/2] uio_hv_generic: Fix sysfs creation path for ring buffer Naman Jain
2025-04-24 5:35 ` [PATCH v6 2/2] Drivers: hv: Make the sysfs node size for the ring buffer dynamic Naman Jain
2025-04-24 13:48 ` [PATCH v6 0/2] uio_hv_generic: Fix ring buffer sysfs creation path Michael Kelley
2025-04-24 16:13 ` Naman Jain
2025-04-25 14:00 ` Greg Kroah-Hartman
2025-04-28 9:07 ` Naman Jain
2025-05-01 16:05 ` Greg Kroah-Hartman
2025-05-02 6:01 ` Naman Jain [this message]
2025-05-02 6:13 ` Greg Kroah-Hartman
2025-05-02 6:17 ` 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=2173d71c-301d-4b6c-b839-0e747d0d0a4b@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