All of lore.kernel.org
 help / color / mirror / Atom feed
From: Imran Khan <imran.f.khan@oracle.com>
To: tj@kernel.org, viro@zeniv.linux.org.uk, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/4] kernfs: make ->attr.open RCU protected.
Date: Thu, 26 May 2022 04:12:15 +1000	[thread overview]
Message-ID: <a41683f3-8d47-2b51-2034-d7b19caf702f@oracle.com> (raw)
In-Reply-To: <20220519072658.736370-1-imran.f.khan@oracle.com>

Hello Tejun,

On 19/5/22 5:26 pm, Imran Khan wrote:
> The patches in this version of the patch set are as follows:
> 
> PATCH-1: Make kernfs_open_node->attr.open RCU protected.
> 
> PATCH-2: Change kernfs_notify_list to llist.
> 
> PATCH-3: Introduce interface to access kernfs_open_file_mutex.
> 
> PATCH-4: Replace global kernfs_open_file_mutex with hashed mutexes.
> 
> Changes since v3:
>  - Rebase on tag next-20220518
>  - Rename RCU access related helpers and update their description
>  - Address errors reported by kernel test robot
>  - Include Acked-by tags from Tejun for the acked patches (PATCH-2,3,4)
> 

I have updated the description of RCU access helpers and have addressed CI
errors as well. Could you please check this and let me know if it looks okay.
Patches 2,3 and 4 have already been acked in earlier version of this this patch
set and they have not changed in this version. It is just Patch 1 that needs
further review. Thanks again for your help.

-- Imran

      parent reply	other threads:[~2022-05-25 18:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-19  7:26 [PATCH v4 0/4] kernfs: make ->attr.open RCU protected Imran Khan
2022-05-19  7:26 ` [PATCH v4 1/4] " Imran Khan
2022-05-19  7:26 ` [PATCH v4 2/4] kernfs: Change kernfs_notify_list to llist Imran Khan
2022-05-19  7:26 ` [PATCH v4 3/4] kernfs: Introduce interface to access global kernfs_open_file_mutex Imran Khan
2022-05-19  7:26 ` [PATCH v4 4/4] kernfs: Replace global kernfs_open_file_mutex with hashed mutexes Imran Khan
2022-05-25 18:12 ` Imran Khan [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=a41683f3-8d47-2b51-2034-d7b19caf702f@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.