Linux filesystem development
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd.schubert@fastmail.fm>
To: Joanne Koong <joannelkoong@gmail.com>,
	miklos@szeredi.hu, linux-fsdevel@vger.kernel.org
Cc: kernel-team@meta.com
Subject: Re: [PATCH v1] fuse: remove unneeded atomic set in uring creation
Date: Tue, 18 Mar 2025 11:34:19 +0100	[thread overview]
Message-ID: <1e770415-cd8a-47b7-944c-62ebacfc9557@fastmail.fm> (raw)
In-Reply-To: <20250318004152.3399104-1-joannelkoong@gmail.com>



On 3/18/25 01:41, Joanne Koong wrote:
> When the ring is allocated, it is kzalloc-ed. ring->queue_refs will
> already be initialized to 0 by default. It does not need to be
> atomically set to 0.
> 
> Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
> ---
>  fs/fuse/dev_uring.c | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/fs/fuse/dev_uring.c b/fs/fuse/dev_uring.c
> index ab8c26042aa8..f54d150330a9 100644
> --- a/fs/fuse/dev_uring.c
> +++ b/fs/fuse/dev_uring.c
> @@ -239,7 +239,6 @@ static struct fuse_ring *fuse_uring_create(struct fuse_conn *fc)
>  	ring->nr_queues = nr_queues;
>  	ring->fc = fc;
>  	ring->max_payload_sz = max_payload_size;
> -	atomic_set(&ring->queue_refs, 0);
>  
>  	spin_unlock(&fc->lock);
>  	return ring;

Thank you, LGTM. I don't remember why I had added that explicit
initialization.

Reviewed-by: Bernd Schubert <bschubert@ddn.com>

      reply	other threads:[~2025-03-18 10:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18  0:41 [PATCH v1] fuse: remove unneeded atomic set in uring creation Joanne Koong
2025-03-18 10:34 ` Bernd Schubert [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=1e770415-cd8a-47b7-944c-62ebacfc9557@fastmail.fm \
    --to=bernd.schubert@fastmail.fm \
    --cc=joannelkoong@gmail.com \
    --cc=kernel-team@meta.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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