The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Imran Khan <imran.f.khan@oracle.com>
To: Tejun Heo <tj@kernel.org>
Cc: viro@zeniv.linux.org.uk, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v4 1/4] kernfs: make ->attr.open RCU protected.
Date: Tue, 14 Jun 2022 12:31:59 +1000	[thread overview]
Message-ID: <e0eb26ab-7c57-6df6-a2ff-83c84ab145a8@oracle.com> (raw)
In-Reply-To: <Yqd0OJupifpplENB@slm.duckdns.org>

Hello Tejun,

On 14/6/22 3:30 am, Tejun Heo wrote:
[...]
> 
> Just merge all three into one accessor. You can list both the !list_empty
> condition and lock held conditions on the same rcu_dereference_check() call.
> 

I have all merged all dereferencing into one accessor in v5 [1] of this
patch-set. Could you please let me know your feedback ?

Thanks
 -- Imran

[1]: https://lore.kernel.org/lkml/20220614020840.546013-1-imran.f.khan@oracle.com/

  reply	other threads:[~2022-06-14  2:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02  6:39 [PATCH RESEND v4 0/4] kernfs: make ->attr.open RCU protected Imran Khan
2022-06-02  6:39 ` [PATCH RESEND v4 1/4] " Imran Khan
2022-06-12 17:58   ` Tejun Heo
2022-06-13  2:36     ` Imran Khan
2022-06-13  2:46       ` Tejun Heo
2022-06-13  2:55         ` Imran Khan
2022-06-13  3:09           ` Tejun Heo
2022-06-13  3:56             ` Imran Khan
2022-06-13 17:30               ` Tejun Heo
2022-06-14  2:31                 ` Imran Khan [this message]
2022-06-02  6:39 ` [PATCH RESEND v4 2/4] kernfs: Change kernfs_notify_list to llist Imran Khan
2022-06-02  6:39 ` [PATCH RESEND v4 3/4] kernfs: Introduce interface to access global kernfs_open_file_mutex Imran Khan
2022-06-02  6:39 ` [PATCH RESEND v4 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=e0eb26ab-7c57-6df6-a2ff-83c84ab145a8@oracle.com \
    --to=imran.f.khan@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@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