[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YFhBHScj4QxLl/Ef@zeniv-ca.linux.org.uk>
Date: Mon, 22 Mar 2021 07:02:53 +0000
From: Al Viro <viro@...iv.linux.org.uk>
To: Namjae Jeon <namjae.jeon@...sung.com>
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-cifs@...r.kernel.org,
linux-cifsd-devel@...ts.sourceforge.net, smfrench@...il.com,
senozhatsky@...omium.org, hyc.lee@...il.com, hch@....de,
hch@...radead.org, ronniesahlberg@...il.com,
aurelien.aptel@...il.com, aaptel@...e.com, sandeen@...deen.net,
dan.carpenter@...cle.com, colin.king@...onical.com,
rdunlap@...radead.org,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Steve French <stfrench@...rosoft.com>
Subject: Re: [PATCH 3/5] cifsd: add file operations
On Mon, Mar 22, 2021 at 02:13:42PM +0900, Namjae Jeon wrote:
> +static struct ksmbd_file *__ksmbd_lookup_fd(struct ksmbd_file_table *ft,
> + unsigned int id)
> +{
> + bool unclaimed = true;
> + struct ksmbd_file *fp;
> +
> + read_lock(&ft->lock);
> + fp = idr_find(ft->idr, id);
> + if (fp)
> + fp = ksmbd_fp_get(fp);
> +
> + if (fp && fp->f_ci) {
> + read_lock(&fp->f_ci->m_lock);
> + unclaimed = list_empty(&fp->node);
> + read_unlock(&fp->f_ci->m_lock);
> + }
> + read_unlock(&ft->lock);
> +
> + if (fp && unclaimed) {
> + atomic_dec(&fp->refcount);
> + return NULL;
> + }
Can that atomic_dec() end up dropping the last remaining reference?
If not, what's to prevent that?
Powered by blists - more mailing lists