From: Anna Schumaker <anna.schumaker@oracle.com>
To: Benjamin Coddington <bcodding@redhat.com>,
Alexander Aring <aahringo@redhat.com>
Cc: trondmy@kernel.org, anna@kernel.org, gregkh@linuxfoundation.org,
rafael@kernel.org, akpm@linux-foundation.org,
linux-nfs@vger.kernel.org, gfs2@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] nfs: kobject: use generic helpers and ownership
Date: Wed, 9 Oct 2024 16:03:35 -0400 [thread overview]
Message-ID: <3a2ce01c-954f-4552-919b-57108509177d@oracle.com> (raw)
In-Reply-To: <A81234BC-0E6D-42AE-BA2B-AF6004DE3C79@redhat.com>
On 10/8/24 4:12 PM, Benjamin Coddington wrote:
> On 3 Oct 2024, at 11:14, Alexander Aring wrote:
>
>> Hi,
>>
>> I currently have pending patches for fs/dlm (Distributed Lock Manager)
>> subsystem to introduce some helpers to udev. However, it seems it takes
>> more time that I can bring those changes upstream. I put those out now
>> and already figured out that nfs can also take advantage of those changes.
>>
>> With this patch-series I try to try to reduce my patch-series for DLM
>> and already bring part of it upstream and nfs will be a user of it.
>>
>> The ownership callback, I think it should be set as the
>> kset_create_and_add() sets this callback as default. I never had any
>> issues with it, but there might be container corner cases that requires
>> those changes?
>>
>> - Alex
>>
>> Alexander Aring (4):
>> kobject: add kset_type_create_and_add() helper
>> kobject: export generic helper ops
>> nfs: sysfs: use kset_type_create_and_add()
>> nfs: sysfs: use default get_ownership() callback
>>
>> fs/nfs/sysfs.c | 30 +++----------------
>> include/linux/kobject.h | 10 +++++--
>> lib/kobject.c | 65 ++++++++++++++++++++++++++++++-----------
>> 3 files changed, 60 insertions(+), 45 deletions(-)
>>
>> --
>> 2.43.0
>
> These look good to me, though patch 4/4 seems superfluous, I responded there.
They look good to me, too. They're not really a bugfix, so they'll probably go in through v6.13 (assuming Trond has no objections, it's his turn to do the merge) and not v6.12-rc.
Anna
>
> For the series:
> Reviewed-by: Benjamin Coddington <bcodding@redhat.com>
>
> Ben
>
prev parent reply other threads:[~2024-10-09 20:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 15:14 [PATCH 0/4] nfs: kobject: use generic helpers and ownership Alexander Aring
2024-10-03 15:14 ` [PATCH 1/4] kobject: add kset_type_create_and_add() helper Alexander Aring
2024-10-03 15:14 ` [PATCH 2/4] kobject: export generic helper ops Alexander Aring
2024-10-03 15:14 ` [PATCH 3/4] nfs: sysfs: use kset_type_create_and_add() Alexander Aring
2024-10-03 15:14 ` [PATCH 4/4] nfs: sysfs: use default get_ownership() callback Alexander Aring
2024-10-08 20:09 ` Benjamin Coddington
2024-10-09 14:56 ` Alexander Aring
2024-10-08 17:36 ` [PATCH 0/4] nfs: kobject: use generic helpers and ownership Alexander Aring
2024-10-08 20:12 ` Benjamin Coddington
2024-10-09 20:03 ` Anna Schumaker [this message]
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=3a2ce01c-954f-4552-919b-57108509177d@oracle.com \
--to=anna.schumaker@oracle.com \
--cc=aahringo@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=anna@kernel.org \
--cc=bcodding@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=trondmy@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