From: Tejun Heo <tj@kernel.org>
To: Imran Khan <imran.f.khan@oracle.com>
Cc: gregkh@linuxfoundation.org, viro@zeniv.linux.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 1/4] kernfs: make ->attr.open RCU protected.
Date: Tue, 14 Jun 2022 20:12:57 -1000 [thread overview]
Message-ID: <Yql4aerFAHyp7ymB@slm.duckdns.org> (raw)
In-Reply-To: <20220615021059.862643-2-imran.f.khan@oracle.com>
On Wed, Jun 15, 2022 at 12:10:56PM +1000, Imran Khan wrote:
> After removal of kernfs_open_node->refcnt in the previous patch,
> kernfs_open_node_lock can be removed as well by making ->attr.open
> RCU protected. kernfs_put_open_node can delegate freeing to ->attr.open
> to RCU and other readers of ->attr.open can do so under rcu_read_(un)lock.
>
> Suggested by: Al Viro <viro@zeniv.linux.org.uk>
> Signed-off-by: Imran Khan <imran.f.khan@oracle.com>
Acked-by: Tejun Heo <tj@kernel.org>
Thanks.
--
tejun
next prev parent reply other threads:[~2022-06-15 6:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 2:10 [PATCH v7 0/4] kernfs: make ->attr.open RCU protected Imran Khan
2022-06-15 2:10 ` [PATCH v7 1/4] " Imran Khan
2022-06-15 6:12 ` Tejun Heo [this message]
2022-06-15 2:10 ` [PATCH v7 2/4] kernfs: Change kernfs_notify_list to llist Imran Khan
2022-07-01 11:22 ` Marek Szyprowski
2022-07-01 12:20 ` Imran Khan
2022-07-01 12:49 ` Marek Szyprowski
2022-07-01 15:06 ` Imran Khan
2022-07-05 15:18 ` Geert Uytterhoeven
2022-06-15 2:10 ` [PATCH v7 3/4] kernfs: Introduce interface to access global kernfs_open_file_mutex Imran Khan
2022-06-15 2:10 ` [PATCH v7 4/4] kernfs: Replace global kernfs_open_file_mutex with hashed mutexes Imran Khan
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=Yql4aerFAHyp7ymB@slm.duckdns.org \
--to=tj@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=imran.f.khan@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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