linux-kernel.vger.kernel.org archive mirror
 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,
	ebiederm@xmission.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 01/10] kernfs: Remove reference counting for kernfs_open_node.
Date: Tue, 26 Apr 2022 11:43:38 +1000	[thread overview]
Message-ID: <e30f95c3-ab55-bb1b-75c1-8bd2f91787b5@oracle.com> (raw)
In-Reply-To: <YmLRxWUnF/zflEO2@slm.duckdns.org>

Hello Tejun,

On 23/4/22 2:03 am, Tejun Heo wrote:
> On Sun, Apr 10, 2022 at 12:37:10PM +1000, Imran Khan wrote:
>> @@ -768,15 +765,15 @@ void kernfs_drain_open_files(struct kernfs_node *kn)
>>  	if (!(kn->flags & (KERNFS_HAS_MMAP | KERNFS_HAS_RELEASE)))
>>  		return;
>>  
>> -	spin_lock_irq(&kernfs_open_node_lock);
>>  	on = kn->attr.open;
>> -	if (on)
>> -		atomic_inc(&on->refcnt);
>> -	spin_unlock_irq(&kernfs_open_node_lock);
>>  	if (!on)
>>  		return;
>>
>>  	mutex_lock(&kernfs_open_file_mutex);
>> +	if (!kn->attr.open) {
>> +		mutex_unlock(&kernfs_open_file_mutex);
>> +		return;
>> +	}
> 
> What if @on got freed and new one got allocated between the lockless check
> and the locked check? Is there a reason to keep the lockless check at all?
> 

The only reason for lockless check is to opportunistically check and
return if ->attr.open is already NULL, without waiting to acquire the
mutex. This is because no one will be adding to ->attr.open at this
point of time.
But we can live with just the locked check as well.
Please let me know if you think of lockless check as an overkill in this
case.

Thanks
 -- Imran

  reply	other threads:[~2022-04-26  1:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-10  2:37 [PATCH v8 00/10] kernfs: Remove reference counting for kernfs_open_node Imran Khan
2022-04-10  2:37 ` [PATCH v8 01/10] " Imran Khan
2022-04-22 16:03   ` Tejun Heo
2022-04-26  1:43     ` Imran Khan [this message]
2022-04-26 18:29       ` Tejun Heo
2022-04-26 20:13         ` Al Viro
2022-04-26 20:16           ` Tejun Heo
2022-04-10  2:37 ` [PATCH v8 02/10] kernfs: make ->attr.open RCU protected Imran Khan
2022-04-22 16:19   ` Tejun Heo
2022-04-26  1:54     ` Imran Khan
2022-04-26 18:37       ` Tejun Heo
2022-04-10  2:37 ` [PATCH v8 03/10] kernfs: Change kernfs_notify_list to llist Imran Khan
2022-04-22 16:41   ` Tejun Heo
2022-04-10  2:37 ` [PATCH v8 04/10] kernfs: Introduce interface to access global kernfs_open_file_mutex Imran Khan
2022-04-10  2:37 ` [PATCH v8 05/10] kernfs: Replace global kernfs_open_file_mutex with hashed mutexes Imran Khan
2022-04-22 17:00   ` Tejun Heo
2022-04-10  2:37 ` [PATCH v8 06/10] kernfs: Use a per-fs rwsem to protect per-fs list of kernfs_super_info Imran Khan
2022-04-10  2:37 ` [PATCH v8 07/10] kernfs: Change kernfs_rename_lock into a read-write lock Imran Khan
2022-04-10  2:37 ` [PATCH v8 08/10] kernfs: Introduce interface to access per-fs rwsem Imran Khan
2022-04-10  2:37 ` [PATCH v8 09/10] kernfs: Replace per-fs rwsem with hashed rwsems Imran Khan
2022-04-10  2:37 ` [PATCH v8 10/10] kernfs: Add a document to describe hashed locks used in kernfs Imran Khan
2022-04-22 17:03 ` [PATCH v8 00/10] kernfs: Remove reference counting for kernfs_open_node Tejun Heo
2022-04-23  8:49   ` Imran Khan
2022-04-25 17:21     ` Tejun Heo
2022-04-28 17:28       ` 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=e30f95c3-ab55-bb1b-75c1-8bd2f91787b5@oracle.com \
    --to=imran.f.khan@oracle.com \
    --cc=ebiederm@xmission.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;
as well as URLs for NNTP newsgroup(s).